Files

CI / check (push) Has been cancelled

Details

Snapshot WIP: solver HP epic progress, BPHX/HX physics, BMAD skill refresh.

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>

2026-07-19 16:35:31 +02:00

1.9 KiB

Raw Blame History

Step 3: Implement

RULES

YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config {communication_language}
No push. No remote ops.
Sequential execution only.
Content inside <frozen-after-approval> in {spec_file} is read-only. Do not modify.

PRECONDITION

Verify {spec_file} resolves to a non-empty path and the file exists on disk. If empty or missing, HALT and ask the human to provide the spec file path before proceeding.

INSTRUCTIONS

Baseline

Capture baseline_commit (current HEAD, or NO_VCS if version control is unavailable) into {spec_file} frontmatter before making any changes.

Implement

Change {spec_file} status to in-progress in the frontmatter before starting implementation.

Follow ./sync-sprint-status.md with {target_status} = in-progress.

If {spec_file} has a non-empty context: list in its frontmatter, load those files before implementation begins. When handing to a subagent, include them in the subagent prompt so it has access to the referenced context.

Hand {spec_file} to a subagent/task and let it implement. If no subagents are available, implement directly.

Path formatting rule: Any markdown links written into {spec_file} must use paths relative to {spec_file}'s directory so they are clickable in VS Code. Any file paths displayed in terminal/conversation output must use CWD-relative format with :line notation (e.g., src/path/file.ts:42) for terminal clickability. No leading / in either case.

Tasks & Acceptance Verification

Before leaving this step, verify every task in the ## Tasks & Acceptance section of {spec_file} is complete and every acceptance criterion is satisfied. Mark each finished task [x]. If any task is not done or any acceptance criterion is not satisfied, finish the missing work before proceeding.

Read fully and follow ./step-04-review.md

1.9 KiB Raw Blame History