writing-plans
Writing Plans
You are creating a detailed execution plan that breaks work into bite-sized tasks. Each task should be small enough that a fresh subagent with no prior context can execute it correctly.
When to Activate
- After brainstorming (if it ran) or directly after issue selection for straightforward work
- When the developer approves the approach and is ready to plan implementation
- NOT for tasks that are already a single atomic change
Preconditions
Before planning, validate inputs exist:
- Design doc (if brainstorming criteria were met): Use Glob to search for
docs/designs/<issue-id>-*.md. If no file is found and brainstorming should have run (the issue met objective complexity criteria), ask the developer via AskUserQuestion: "No design document found for this issue. Run brainstorming first, provide a design doc path, or proceed without one?" - Issue ID available: Confirm the issue ID is available from session-start or
$ARGUMENTS. If missing, ask the developer.
After preconditions pass, print the activation banner (see _shared/observability.md):
More from brite-nites/britenites-claude-plugins
verification-before-completion
Ensures tasks are genuinely resolved before marking them done. Activates at task checkpoints during plan execution — validates that fixes actually work, tests genuinely pass, and acceptance criteria are met. Prevents premature completion declarations.
16systematic-debugging
Four-phase root cause analysis for bug investigation. Activates when debugging unexpected behavior, failing tests, or production issues — follows reproduce, isolate, analyze, fix with defense-in-depth. Uses condition-based waiting instead of arbitrary delays. Available anytime, not tied to the inner loop sequence.
14refine-plan
Refines a v1 project plan into agent-ready tasks with clear context, implementation steps, and validation criteria. Use after /plan-project has produced a v1 plan.
13setup-claude-md
Generates a best-practices CLAUDE.md file for the project. Analyzes the codebase and applies Claude Code best practices for optimal agent performance. Use at project setup or after /create-issues.
13executing-plans
Executes a structured plan using subagent-per-task with TDD enforcement. Activates when given an approved plan to implement — launches fresh subagents for each task, enforces red-green-refactor, runs two-stage review per task, and checkpoints between tasks. Parallelizes independent tasks.
13git-worktrees
Creates an isolated git worktree for task execution. Activates when starting work on a planned issue — sets up a new branch with Linear issue ID, runs project setup, and verifies a clean test baseline before coding begins.
12