* enh(#3565): sentinel/contract registry + check:contract-drift lint * fix(#3565): report artifact-row markers once and dedupe per marker * docs(#3565): backfill changeset pr number --------- Co-authored-by: sim <sim@local>
This commit is contained in:
@@ -224,8 +224,6 @@ This is the single entry point `gsd-roadmapper` reads.
|
||||
Return ≤ 10 lines to the orchestrator:
|
||||
|
||||
```
|
||||
## Synthesis Complete
|
||||
|
||||
Docs synthesized: {N} ({breakdown})
|
||||
Decisions locked: {N}
|
||||
Requirements: {N}
|
||||
|
||||
@@ -8,6 +8,9 @@ color: cyan
|
||||
|
||||
<role>
|
||||
You are the MemPalace curator. You run once per phase at `ship:post`, after verification has passed, to consolidate the phase's memory into the palace. Everything you do is best-effort and wing-scoped: a MemPalace failure must never fail the ship step (`onError: skip`), and you must never touch drawers outside this project's wing.
|
||||
|
||||
**CRITICAL: Mandatory Initial Read**
|
||||
If the prompt contains a `<required_reading>` block, you MUST use the `Read` tool to load every file listed there before performing any other actions. This is your primary context.
|
||||
</role>
|
||||
|
||||
<inputs>
|
||||
|
||||
@@ -915,6 +915,40 @@ See @~/.claude/gsd-core/references/planner-chunked.md for `## OUTLINE COMPLETE`
|
||||
|
||||
<success_criteria>
|
||||
|
||||
## Return Markers
|
||||
|
||||
Your orchestrator dispatches on exact marker strings in your final output. Emit exactly one of:
|
||||
|
||||
```markdown
|
||||
## PLANNING COMPLETE
|
||||
```
|
||||
(final plans committed, ready for verification)
|
||||
|
||||
```markdown
|
||||
## OUTLINE COMPLETE
|
||||
```
|
||||
(outline produced, awaiting confirmation — chunked planning mode)
|
||||
|
||||
```markdown
|
||||
## PHASE SPLIT RECOMMENDED
|
||||
```
|
||||
(phase too large to plan as one unit, include the proposed split)
|
||||
|
||||
```markdown
|
||||
## ⚠ Source Audit
|
||||
```
|
||||
(unplanned items found in the requirements, include the options)
|
||||
|
||||
```markdown
|
||||
## CHECKPOINT REACHED
|
||||
```
|
||||
(paused at a user checkpoint, include resume instructions)
|
||||
|
||||
```markdown
|
||||
## PLANNING INCONCLUSIVE
|
||||
```
|
||||
(cannot produce a plan, include exactly what is missing)
|
||||
|
||||
## Standard Mode
|
||||
|
||||
Phase planning complete when:
|
||||
|
||||
@@ -13,6 +13,9 @@ You are spawned by the profile orchestration workflow (Phase 3) or by write-prof
|
||||
Your job: Apply the heuristics defined in the user-profiling reference document to score each dimension with evidence and confidence. Return structured JSON analysis.
|
||||
|
||||
CRITICAL: You must apply the rubric defined in the reference document. Do not invent dimensions, scoring rules, or patterns beyond what the reference doc specifies. The reference doc is the single source of truth for what to look for and how to score it.
|
||||
|
||||
**CRITICAL: Mandatory Initial Read**
|
||||
If the prompt contains a `<required_reading>` block, you MUST use the `Read` tool to load every file listed there before performing any other actions. This is your primary context.
|
||||
</role>
|
||||
|
||||
<input>
|
||||
|
||||
Reference in New Issue
Block a user