From 48576c59d2dca2e80018f2dab543dd9a8618aee4 Mon Sep 17 00:00:00 2001 From: Sawyer Cutler Date: Thu, 22 Oct 2026 17:09:01 -0700 Subject: [PATCH] fix(prompts): synthesize requirements in planner card --- packages/prompt-fragments/src/cards.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/prompt-fragments/src/cards.ts b/packages/prompt-fragments/src/cards.ts index 6f0a28c66..d3d1d6669 100644 --- a/packages/prompt-fragments/src/cards.ts +++ b/packages/prompt-fragments/src/cards.ts @@ -80,7 +80,7 @@ Core artifacts: Workflow: 1. Clarify requirements: read the brief's goals and success_criteria. If critical unknowns remain, ask the parent via ask_director; otherwise resolve ambiguity under explicit Assumptions. 2. Inspect the codebase: read relevant paths, existing contracts, and test patterns to ground the plan in reality. -3. Produce the plan: author the requested artifacts (PRD.md / SOLUTION_SCOPE.md / BUILD_PLAN.md when requested, or include the structured plan directly in Findings). +3. Produce the plan: author the requested artifacts (PRD.md / SOLUTION_SCOPE.md / BUILD_PLAN.md when requested, or include the structured plan directly in Findings). Synthesize iterative operator turns into a unified domain model and requirement set — do not append chronological chat turns as separate rows. State non-goals and deferred scope once in SOLUTION_SCOPE.md (or one section header), never as repeated per-row disclaimers. 4. Report: use the standard ${REPORT_ENVELOPE_SHAPE} report envelope. Findings must carry the complete ordered plan, acceptance criteria, non-goals, and risks. ${outOfLane("shipping product implementation code, executing test suites for product verification, fleet orchestration or spawning, becoming Coder or Reviewer as primary")}`;