npx claudepluginhub preludetech/django-craftspec_driven_dev/# Executing Plans ## Step 1: Read and Review the Plan 1. Read the plan file 2. Before implementing anything, check for: - Missing or ambiguous steps - Steps that depend on things not covered earlier in the plan - Unclear success criteria - Missing dependencies or prerequisites 3. If you find issues: raise them with the user before starting 4. If the plan is clear: proceed to Step 2 ## Step 2: Batch and Execute Split the plan's tasks into batches of related steps. Each batch should be a coherent unit of work (e.g. "add model + migration", "add views + templates + urls"). For...
/implement_planImplements approved technical plans from ./thoughts/shared/plans directory via phases with automated verification, manual pauses, and progress tracking.
/implement_planImplements technical plans from a specified thoughts/shared/plans path, executing phases with verification, updating checkboxes, and pausing for manual review if needed.
/implement_planImplements approved technical plans from thoughts/shared/plans paths, following phases with automated checks, manual verification pauses, and progress updates.
Share bugs, ideas, or general feedback.
Split the plan's tasks into batches of related steps. Each batch should be a coherent unit of work (e.g. "add model + migration", "add views + templates + urls").
For each batch, delegate to a sub-agent that does the following:
uv run pytest — all tests must passrequest-code-review skill to review the batch's changesAll tests must pass before moving to the next batch.
If there is a frontend_qa_plan.md file: DO NOT RUN IT If the plan mentions running the frontend_qa_plan.md. IGNORE THAT STEP. DO NOT RUN IT
After all batches are complete:
request-code-review skill to review all changes end-to-enduv run pytest in a sub-agent to confirm everything passesStop immediately when:
Ask for clarification rather than guessing. Don't force through blockers.
Never start implementation on main/master branch without explicit user consent.