fix(quick-dev): mark task checkboxes during implementation

[alexeyv]

Summary

• Adds a Self-Check gate at the end of step-03-implement.md that forces the implementing agent to verify all tasks are complete and mark checkboxes [x] before handing off to the review step
• Prevents the agent from moving to step-04 without confirming it finished everything

Test plan

• Run quick-dev workflow through step-03 and verify all task checkboxes are marked in the spec file before step-04 begins

[augmentcode]

🤖 Augment PR Summary

Summary: Updates the quick-dev implementation step to explicitly track completion of spec tasks during development.

Changes:

• Added an instruction in step-03-implement.md to mark completed checkboxes as [x] in the spec’s ## Tasks & Acceptance section, improving real-time progress visibility.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. No suggestions at this time.

Comment augment review to trigger a new review at any time.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds task-tracking instructions to the implementation guide, requiring tasks in the "Tasks & Acceptance" section to be marked as completed by checking their checkboxes [x] during implementation of specification files.

Changes

Cohort / File(s)	Summary
Documentation Update src/bmm-skills/4-implementation/bmad-quick-dev/step-03-implement.md	Added task-tracking instructions specifying that completed tasks must be marked with [x] and incomplete tasks remain unchecked.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

• bmadcode

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly describes the main change: adding task-tracking instructions for marking checkboxes during implementation in the quick-dev workflow.
Description check	✅ Passed	The description clearly explains the purpose and implementation approach for marking task checkboxes, with a defined test plan related to the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/checkbox-tracking

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Tip

You can enable review details to help with troubleshooting, context usage and more.

Enable the reviews.review_details setting to include review details such as the model used, the time taken for each step and more in the review comments.

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/bmm-skills/4-implementation/bmad-quick-dev/step-03-implement.md`:
- Around line 29-30: The PR introduces live checkbox state updates in the
workflow described in
src/bmm-skills/4-implementation/bmad-quick-dev/step-03-implement.md but does not
update documentation; add a docs change under docs/ that explains the new
behavior (how the "Tasks & Acceptance" section checkboxes update live, any
UI/state implications, and expected user interactions), reference the exact
workflow and section name ("## Tasks & Acceptance") so readers can correlate,
and include any developer notes about implementation details or API/prop changes
required to support the live updates.
- Around line 29-30: The new checkbox-update requirement conflicts with the
read-only frozen rule (<frozen-after-approval>); add an explicit exception that
permits agents to toggle task checkboxes only inside the "## Tasks & Acceptance"
section (or introduce a scoped tag such as <mutable-tasks> around that section)
so that checkbox state changes are allowed while all other fields under
<frozen-after-approval> remain immutable; update validation/enforcement logic to
ignore checkbox modifications inside that scoped section and enforce
immutability elsewhere, and reference the section title "## Tasks & Acceptance"
and the symbol <frozen-after-approval> in the change so reviewers can locate and
verify the exception.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 8693de45-44f4-4aba-8961-ee226a46108b

📥 Commits

Reviewing files that changed from the base of the PR and between 76fb7e0 and 744c60c.

📒 Files selected for processing (1)

• src/bmm-skills/4-implementation/bmad-quick-dev/step-03-implement.md