poe-code 3.0.25 → 3.0.26

package/dist/index.js

@@ -14694,21 +14694,21 @@ var require_dist = __commonJS({
 // src/templates/ralph/PROMPT_PARTIAL_plan.md
 var require_PROMPT_PARTIAL_plan = __commonJS({
   "src/templates/ralph/PROMPT_PARTIAL_plan.md"(exports, module) {
-    module.exports = '# Plan Generation\n\nYou are an agent that generates a Ralph PRD file (YAML) based on a user request.\n\n## Requirements\n- Create (or overwrite) the file at the output path.\n- The file must be valid YAML.\n- Use this structure (minimum):\n  - version: 1\n  - project: <short name>\n  - overview: <1-3 paragraphs>\n  - goals: [ ... ]\n  - nonGoals: [ ... ]\n  - qualityGates:\n    - npm run test\n    - npm run lint\n  - stories: [ ... ]\n- Stories should be actionable, small, and testable. Keep it to one story per atomic feature.\n- Each story must include:\n  - id: "US-###" (sequential, starting at US-001)\n  - title\n  - status: open\n  - dependsOn: [] (or list of story IDs)\n  - description: "As a user, I want ..."\n  - acceptanceCriteria: ["...", "..."]\n\n## If The Request Is Empty\nAsk the user for a one-sentence description of what they want to build.\n\n## Validation\nAfter writing the plan file, validate it by running:\n```\npoe-code ralph agent validate-plan --plan <output-path>\n```\nIf validation fails, fix the errors and re-validate until the plan passes.\n\n## Done Signal\nAfter the plan is validated, print a single line confirming the path, e.g.:\n```\nWrote plan to <output-path>\n```\n';
+    module.exports = "# Plan Generation\n\nYou are an agent that generates a Ralph PRD file (YAML) based on a user request. Your ONLY output is a plan file \u2014 do NOT write or modify any code. Follow these phases in order. Keep each phase tight\u2014write only what's needed to move forward.\n\n---\n\n## Phase 1: Understand\n\nBefore touching code, understand the problem and the codebase.\n\n- **Read first.** Never propose changes to code you haven't read. Search for existing patterns, utilities, and conventions.\n- **Ask why.** What problem does this solve? Why now? What happens if we don't do it?\n- **Challenge assumptions.** Question the framing. Restate the problem in your own words.\n- **Visualize.** Use ASCII diagrams for architecture, data flow, state machines\u2014whenever structure aids clarity.\n- **Surface unknowns.** What could go wrong? What don't we know yet? What needs investigation?\n\nStay here until the problem shape is clear. Don't rush to solutions.\n\n---\n\n## Phase 2: Propose\n\nEstablish scope and intent. Write a short proposal:\n\n- **Why**: 1-2 sentences. The problem or opportunity.\n- **What changes**: Bullet list of concrete changes. Be specific.\n- **Impact**: What code, APIs, systems, or users are affected.\n\nKeep it to half a page. Focus on the \"why\" not the \"how.\"\n\n---\n\n## Phase 3: Specify\n\nDefine **what** the system should do in testable terms.\n\nFor each new or changed behavior, write requirements:\n\n```\n### Requirement: <name>\n<Description using precise language \u2014 SHALL, MUST for normative statements>\n\n#### Scenario: <name>\n- WHEN <condition>\n- THEN <expected outcome>\n```\n\nRules:\n\n- Every requirement needs at least one scenario.\n- Scenarios are test cases. If you can't write a scenario, the requirement isn't clear enough.\n- For modifications to existing behavior, state the full updated requirement, not just the diff.\n\n---\n\n## Phase 4: Design\n\nExplain **how** you'll build it. Only include this for non-trivial changes (cross-cutting, new dependencies, architectural decisions, ambiguity worth resolving upfront).\n\n- **Context**: Current state, constraints.\n- **Goals / Non-goals**: What's in scope and what's explicitly out.\n- **Decisions**: Key technical choices. For each: what you chose, what you rejected, and why.\n- **Risks / Trade-offs**: What could go wrong \u2192 how you'll mitigate it.\n\nFocus on architecture and approach. Don't describe every line of code.\n\n---\n\n## Phase 5: Tasks\n\nBreak the work into stories and write the plan YAML file.\n\n### YAML Structure\n\n- Create (or overwrite) the file at the output path.\n- The file must be valid YAML.\n- Use this structure (minimum):\n  - version: 1\n  - project: <short name>\n  - overview: <1-3 paragraphs \u2014 include the proposal from Phase 2 and key design decisions from Phase 4>\n  - goals: [ ... ]\n  - nonGoals: [ ... ]\n  - qualityGates:\n    - npm run test\n    - npm run lint\n  - requirements: [ ... ] (from Phase 3, each with scenarios)\n  - stories: [ ... ]\n\n### Stories\n\n- Stories should be actionable, small, and testable. Keep it to one story per atomic feature.\n- Each story must include:\n  - id: \"US-###\" (sequential, starting at US-001)\n  - title\n  - status: open\n  - dependsOn: [] (or list of story IDs)\n  - description: \"As a user, I want ...\"\n  - acceptanceCriteria: [\"...\", \"...\"] (derived from Phase 3 scenarios)\n\n---\n\n## Validation\n\nAfter writing the plan file, validate it by running:\n\n```\npoe-code ralph agent validate-plan --plan <output-path>\n```\n\nIf validation fails, fix the errors and re-validate until the plan passes.\n\n## Done Signal\n\nAfter the plan is validated, print a single line confirming the path, e.g.:\n\n```\nWrote plan to <output-path>\n\nRun `poe-code ralph build`\n\n```\n";
   }
 });
 
 // src/templates/ralph/SKILL_plan.md
 var require_SKILL_plan = __commonJS({
   "src/templates/ralph/SKILL_plan.md"(exports, module) {
-    module.exports = "---\nname: poe-code-ralph-plan\ndescription: 'Generate a Ralph plan (YAML) from a user request. Triggers on: create a plan, write plan for, plan this feature, ralph plan.'\n---\n\n{{{PROMPT_PARTIAL_PLAN}}}\n\n## User Request\n\nThe user's request follows this skill invocation. Use it to determine what to build.\n\n## Output Path\n\nWrite the YAML file to `.agents/tasks/plan-<name>.yaml` unless the user specifies a different path.\n";
+    module.exports = "---\nname: poe-code-ralph-plan\ndescription: 'Generate a Ralph plan (YAML) from a user request. Triggers on: create a plan, write plan for, plan this feature, ralph plan.'\n---\n\n## If The Request Is Empty\n\nAsk the user for a one-sentence description of what they want to build.\n\n{{{PROMPT_PARTIAL_PLAN}}}\n\n## Output Path\n\nWrite the YAML file to `.agents/tasks/plan-<name>.yaml` unless the user specifies a different path.\n";
   }
 });
 
 // src/templates/ralph/PROMPT_plan.md
 var require_PROMPT_plan = __commonJS({
   "src/templates/ralph/PROMPT_plan.md"(exports, module) {
-    module.exports = "{{{PROMPT_PARTIAL_PLAN}}}\n\n## User Request\n{{REQUEST}}\n\n## Output Path\nWrite the YAML file to:\n{{OUT_PATH}}\n";
+    module.exports = "{{{PROMPT_PARTIAL_PLAN}}}\n\n## User Request\n\n{{REQUEST}}\n\n## Output Path\n\nWrite the YAML file to:\n{{OUT_PATH}}\n";
   }
 });