Dev Implement

Pre-Execution

Identify Target Task

1. Read the task file with the Read tool.
2. Find the target parent task.
3. Announce: [PRE-FLIGHT CHECK] Target: parent task {Number} ('{Name}'). Reply 'Go' to begin.
4. HALT AND AWAIT confirmation.

Environment Validation

• Use Shell to check tool versions and environment readiness.
• Announce detected infrastructure.

The Execution Loop

WHILE unchecked [ ] sub-tasks exist for the current parent task:

Step 1: Context Loading

1. Find the first unchecked [ ] sub-task.
2. Read the [APPLIES RULES: ...] directive. Use Read to load each referenced rule file from .cursor/rules/.
3. Announce: [CONTEXT LOADED] Applying rules: {list}.
4. If the sub-task involves a specific platform, use WebSearch or WebFetch to consult official docs.
5. Announce: [NEXT TASK] {number and name}.

Step 2: Execution

1. Use Write, StrReplace, Shell tools to perform ONLY what the sub-task asks.
2. Avoid over-engineering. Implement the simplest correct solution.
3. Self-verify all criteria are met.
4. Integrated Quick Review:
   • Security/architecture changes: validate immediately.
   • Database changes: verify migrations, rollback, data integrity.
   • UI changes: verify build compatibility, asset loading.
5. Settings Wiring: If task involves settings keys, use Grep to verify UI keys match backend keys exactly.
6. On error: STOP immediately. Do NOT mark complete. Report and await instructions.

Step 3: Update and Sync

1. Update Task File: Use StrReplace to change [ ] to [x]. This is NON-NEGOTIABLE before any git operations.
2. Granular Commits: After each functional unit, propose a commit.
   • Format: {type}({scope}): {brief description}
   • Examples: feat(iam): implement role inheritance, test(gateway): add e2e tests
3. Parent Task Completion:
   • Verify README updates.
   • Run quality gate: [QUALITY GATE] Running audit...
   • Report: [QUALITY REPORT] Score: X/10. Critical: Y, High: Z. Status: PASS/NEEDS_ATTENTION
   • Git strategy: [GIT STRATEGY] Options: (A) Keep granular commits (B) Squash. Recommend: {A/B}. Confirm?
   • HALT and await.

Step 4: Checkpoint

• Focus Mode: Task {N} complete. Quick review: PASSED. Commit: {hash}. Continue?
• Continuous Mode: Report at parent task completion only.

Communication Prefixes

Use exclusively: [NEXT TASK], [TASK COMPLETE], [CONTEXT LOADED], [QUALITY GATE], [QUALITY REPORT], [PRE-FLIGHT CHECK], [FEATURE CHECK], [GIT STRATEGY], [EMERGENCY ROLLBACK].

Factual and direct. No pleasantries. During halts, do not ask open-ended questions.

Next Step

After all parent tasks complete, proceed to the dev-retro skill for the implementation retrospective.