Some checks failed
CI / check (push) Has been cancelled
Capture uncommitted solver robustness work (regularization, domain errors, linear solver lifecycle, tube DP/MSH), web workbench updates, and synced BMAD skills across IDE agent folders before starting BPHX pressure-drop. Co-authored-by: Cursor <cursoragent@cursor.com>
2.1 KiB
2.1 KiB
deferred_work_file
| deferred_work_file |
|---|
| {implementation_artifacts}/deferred-work.md |
Step 2: Plan
RULES
- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config
{communication_language} - No human interaction: do not ask questions or wait for approval in this step.
INSTRUCTIONS
- Draft resume check. If
{spec_file}exists withstatus: draft, read it and capture the verbatim<intent-contract>...</intent-contract>block aspreserved_intent_contract. Otherwisepreserved_intent_contractis empty. - Investigate codebase. Use subagents for deep exploration. To prevent context snowballing, instruct subagents to give you distilled summaries only.
- Read
./spec-template.mdfully. Fill it out based on the intent and investigation. If{preserved_intent_contract}is non-empty, substitute it for the<intent-contract>block in your filled spec before writing. Write the result to{spec_file}. - Self-review against READY FOR DEVELOPMENT standard.
- If intent gaps exist, do not fantasize and do not leave open questions. HALT with status
blocked, blocking conditionintent gaps, and include the unanswered questions and evidence gathered. - Warning check. If step-01 carried
multiple-goals, add it to{spec_file}frontmatterwarnings. If{spec_file}exceeds 1600 tokens, addoversizedto frontmatterwarnings. Continue either way.
READY-FOR-DEVELOPMENT GATE
Re-read ./SKILL.md, then re-read {spec_file} from disk and verify the spec meets the READY FOR DEVELOPMENT standard.
- If the file is missing: HALT with status
blockedand blocking conditionplanned spec file disappeared before implementation. - If the spec meets the standard: set
{spec_file}frontmatter status toready-for-dev, then continue to step 3. - If the spec does not meet the standard: repair it once, then re-read it from disk and verify again. If it still does not meet the standard, HALT with status
blocked, blocking conditionspec failed ready-for-development standard, and include the failing criteria and evidence gathered.
NEXT
Read fully and follow ./step-03-implement.md