USE when creating project plans, BRIEF.md, ROADMAP.md, or phase PLAN.md documents. Defines project planning standards, document templates (BRIEF, ROADMAP, PLAN), and format specifications for structured execution.
/plugin marketplace add Git-Fg/thecattoolkit/plugin install sys-builder@cattoolkitThis skill is limited to using the following tools:
assets/templates/brief.mdassets/templates/discovery.mdassets/templates/handoff.mdassets/templates/issue-entry.mdassets/templates/issues.mdassets/templates/phase-plan.mdassets/templates/roadmap.mdassets/templates/summary.mdreferences/context-management.mdreferences/plan-format.mdFor user-invoked planning, use /create-plan skill.
For user-invoked execution, use /execute-plan skill.
This skill provides templates and standards. The create-plan and execute-plan skills are the primary user-facing interfaces.
ALL planning artifacts MUST be created in:
.cattoolkit/planning/{project-slug}/
NEVER create PLAN.md, ROADMAP.md, BRIEF.md at project root.
This is enforced by the create-plan skill and must be followed by all planning workflows.
This skill defines WHAT documents to create and their structure.
It answers: "What templates and formats should I use?" (not "How to execute them").
HOW to execute is defined by execution-core skill (Uninterrupted Flow, Self-Verification, Handoffs).
Document Templates:
assets/templates/brief.md - Project brief (v1.0 greenfield, v1.1+ brownfield)assets/templates/roadmap.md - Project roadmap with phasesassets/templates/phase-plan.md - Executable phase plansassets/templates/handoff.md - Session handoff templateassets/templates/summary.md - Phase completion summaryassets/templates/issues.md - Deferred enhancements trackingassets/templates/issue-entry.md - Individual issue templateassets/templates/discovery.md - Project discovery templateFormat Standards:
references/plan-format.md - PLAN.md structure guidelinesreferences/context-management.md - Context organization in plans| Document Type | Template Location | Use Case |
|---|---|---|
| Project Brief | assets/templates/brief.md | Project starts (v1.0) or iterations (v1.1+) |
| Roadmap | assets/templates/roadmap.md | Multi-phase projects |
| Phase Plan | assets/templates/phase-plan.md | Executable phases |
| Handoff | assets/templates/handoff.md | Session pauses mid-phase |
| Summary | assets/templates/summary.md | Phase completions |
| Issues | assets/templates/issues.md | Deferred enhancements |
Project Documents: .cattoolkit/planning/{project-slug}/
assets/templates/brief.mdassets/templates/roadmap.mdassets/templates/issues.mdPhase Documents: .cattoolkit/planning/{project-slug}/phases/XX-name/
assets/templates/phase-plan.mdassets/templates/summary.mdassets/templates/handoff.mdStandard Format for Documents:
BRIEF.md:
---
project: [Project Name]
version: 1.0
status: in_progress
---
ROADMAP.md:
---
project: [Project Name]
version: 1.0
status: in_progress
---
PLAN.md:
---
phase: XX-name
type: execute
status: in_progress
---
Valid Status Values: in_progress, completed
Greenfield (v1.0):
Brownfield (v1.1+):
See assets/templates/brief.md for full template.
Initial Planning (v1.0):
{phase}-{plan}-PLAN.mdAfter Milestones:
<details> tagsSee assets/templates/roadmap.md for full template.
Structure Requirements:
Task Standards:
See references/plan-format.md for detailed task structure guidelines.
Purpose: Enable "State-in-Files" architecture when pausing mid-phase
Triggers:
Requirements:
See assets/templates/handoff.md for full template.
SUMMARY.md Compliance:
HANDOFF.md Compliance:
This skill defines WHAT to create. HOW to execute is in execution-core:
execution-core/references/observation-points.mdexecution-core/references/observation-points.mdexecution-core/references/auth-gates.mdexecution-core/references/handoff-protocol.mdExample Integration:
When creating a PLAN.md:
assets/templates/phase-plan.md for structure (project-strategy)execution-core (HOW to behave)
↓
project-strategy (WHAT documents to create)
↓
director/worker agents (Execute using these standards)
Commands reference project-strategy for document standards:
Example from /plan command:
Use project-strategy templates to create BRIEF.md and ROADMAP.md
Validate plan structure against project-strategy specifications
Example from /execute command:
Use project-strategy PLAN.md format for phase execution
Reference execution-core for behavioral protocols during execution
Trigger: User requests a new project plan ("Create a plan for...", "I need a roadmap for...").
Action: Analyze the request and available context to extract:
Sources to check:
.cattoolkit/planning/If critical information is missing: Make a Strategic Assumption and document it clearly in the plan output. If entirely blocked, create HANDOFF.md per execution-core protocol.
Action: If this is an existing codebase, perform discovery:
DISCOVERY.md.Determine Plan Type:
PLAN.md directly.BRIEF.md, ROADMAP.md, Phase PLAN.mds).Lite Plan:
PLAN.md using assets/templates/phase-plan.md structure.Standard Plan:
BRIEF.md (Project goals).ROADMAP.md (Phases and milestones)..cattoolkit/planning/...).PLAN.md for Phase 1.This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.