plan.mdtech-stack.md before implementationCI=true for watch-mode tools (tests, linters) to ensure single execution.All tasks follow a strict lifecycle:
Select Task: Choose the next available task from plan.md in sequential order
Mark In Progress: Before beginning work, edit plan.md and change the task from [ ] to [~]
Write Failing Tests (Red Phase):
Implement to Pass Tests (Green Phase):
Refactor (Optional but Recommended):
Document Deviations: If implementation differs from tech stack:
tech-stack.md with new designCommit Code Changes:
feat(ui): Create basic HTML structure for calculator.Attach Task Summary with Git Notes:
git log -1 --format="%H").git notes command to attach the summary to the commit.# The note content from the previous step is passed via the -m flag. git notes add -m "<note content>" <commit_hash>
Get and Record Task Commit SHA:
plan.md, find the line for the completed task, update its status from [~] to [x], and append the first 7 characters of the just-completed commit's commit hash.plan.md.Commit Plan Update:
plan.md file.conductor(plan): Mark task 'Create user model' as complete).Trigger: This protocol is executed immediately after a task is completed that also concludes a phase in plan.md.
Announce Protocol Start: Inform the user that the phase is complete and the verification and checkpointing protocol has begun.
Ensure Test Coverage for Phase Changes:
plan.md to find the Git commit SHA of the previous phase's checkpoint. If no previous checkpoint exists, the scope is all changes since the first commit.git diff --name-only <previous_checkpoint_sha> HEAD to get a precise list of all files modified during this phase..json, .md, .yaml).plan.md).Execute Automated Tests with Proactive Debugging:
CI=true npm test”Propose a Detailed, Actionable Manual Verification Plan:
CRITICAL: To generate the plan, first analyze product.md, product-guidelines.md, and plan.md to determine the user-facing goals of the completed phase.
You must generate a step-by-step plan that walks the user through the verification process, including any necessary commands and specific, expected outcomes.
The plan you present to the user must follow this format:
For a Frontend Change:
The automated tests have passed. For manual verification, please follow these steps: **Manual Verification Steps:** 1. **Start the development server with the command:** `npm run dev` 2. **Open your browser to:** `http://localhost:3000` 3. **Confirm that you see:** The new user profile page, with the user's name and email displayed correctly.
For a Backend Change:
The automated tests have passed. For manual verification, please follow these steps:
**Manual Verification Steps:**
1. **Ensure the server is running.**
2. **Execute the following command in your terminal:** `curl -X POST http://localhost:8080/api/v1/users -d '{"name": "test"}'`
3. **Confirm that you receive:** A JSON response with a status of `201 Created`.
Await Explicit User Feedback:
Create Checkpoint Commit:
conductor(checkpoint): Checkpoint end of Phase X).Attach Auditable Verification Report using Git Notes:
git notes command and the full commit hash from the previous step to attach the full report to the checkpoint commit.Get and Record Phase Checkpoint SHA:
git log -1 --format="%H").plan.md, find the heading for the completed phase, and append the first 7 characters of the commit hash in the format [checkpoint: <sha>].plan.md.Commit Plan Update:
plan.md file.conductor(plan): Mark phase '<PHASE NAME>' as complete.Announce Completion: Inform the user that the phase is complete and the checkpoint has been created, with the detailed verification report attached as a git note.
Before marking any task complete, verify:
code_styleguides/)./gen.py && ninja -C out $TARGETS, where targets can be gn or gn_unittests for the tool or the tests respectively.out/gn_unittestsutil/test/test.h so you can use standard gtest filters to only run specific tests.Before requesting review:
Functionality
Code Quality
Testing
<type>(<scope>): <description> [optional body] [optional footer]
feat: New featurefix: Bug fixdocs: Documentation onlystyle: Formatting, missing semicolons, etc.refactor: Code change that neither fixes a bug nor adds a featuretest: Adding missing testschore: Maintenance tasksgit commit -m "feat(auth): Add remember me functionality" git commit -m "fix(posts): Correct excerpt generation for short posts" git commit -m "test(comments): Add tests for emoji reaction limits" git commit -m "style(mobile): Improve button touch targets"
A task is complete when:
plan.md