refine-plan
Instructions
You are refining a v1 project plan into agent-ready tasks.
Input
- Read the v1 plan. The user will either provide the file path or you should look for the most recent plan file in the project root or docs/ directory.
Process
-
Analyze the plan using sequential-thinking MCP:
- Identify all distinct pieces of work
- Determine dependencies between them
- Identify the optimal execution order
- Flag any ambiguities or gaps in the v1 plan
-
For each task, produce:
- Title: Clear, action-oriented (e.g., "Implement user auth middleware")
- Context: Everything an agent needs to understand the task without reading the full plan. Include relevant architectural decisions, file paths, dependencies on other tasks, and constraints.
- Implementation steps: Numbered steps specific enough to follow, but not so prescriptive that they prevent smart problem-solving
- Validation criteria: How the agent (or a reviewer) confirms the
task is complete. Should include at minimum:
- What to test / run
- Expected output or behavior
- Edge cases to verify
- Estimated complexity: S / M / L
- Dependencies: List of task IDs this depends on
-
Add a "Task 0" at the top of the plan:
- Title: "Generate Linear issues and update CLAUDE.md"
- Description: Instructions to run
/create-issuesfollowed by/setup-claude-md - This ensures the first thing an engineer does is set up the project infrastructure
Output
- Write the refined plan to
docs/project-plan-refined.md - Use a consistent markdown structure (template below)
Output Template
# [Project Name] — Refined Plan
## Summary
[1-2 sentence summary of the project]
## Task Dependency Graph
[Mermaid diagram showing task dependencies]
## Tasks
### Task 0: Generate Linear Issues and Update CLAUDE.md
- **Context**: [...]
- **Steps**: Run `/create-issues docs/project-plan-refined.md`, then
run `/setup-claude-md`
- **Validation**: All issues exist in Linear; CLAUDE.md passes best
practices checklist
### Task 1: [Title]
- **Context**: [...]
- **Steps**: [...]
- **Validation**: [...]
- **Complexity**: [S/M/L]
- **Dependencies**: [None | Task IDs]
[...repeat for all tasks]
Validation Criteria
Read .claude/skills/_shared/validation-pattern.md and apply it.
Specific criteria for this skill:
- Every task has all required fields filled in (title, context, steps, validation, complexity, dependencies)
- An agent reading any single task would have enough context to start working without asking clarifying questions
- Dependencies form a valid DAG (no circular dependencies)
- Task 0 is present and correctly references the next skills
- The refined plan covers all work items from the v1 plan (nothing dropped)
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.
16setup-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.
13post-plan-setup
Runs the full post-plan workflow. Refine plan, create Linear issues, setup CLAUDE.md. Use after /plan-project produces a v1 plan. Pauses between phases for optional review.
12python-best-practices
Use when writing, reviewing, or refactoring FastAPI/Python backend code. Triggers on FastAPI endpoints, Pydantic models, SQLAlchemy queries, async Python code, or Python API architecture. Contains 38 architectural rules across 8 categories.
12ui-ux-pro-max
Design system generation and UI/UX planning intelligence. Use when the user needs to choose a color palette, select fonts, generate a design system, plan a visual direction, or explore UI styles before implementation. Covers 50+ styles, 97 palettes, 57 font pairings across 9 stacks. Do NOT use for building/coding UI — use frontend-design for implementation.
11web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
11