Project planning standards, document templates, and format specifications. Defines WHAT documents to create (BRIEF, ROADMAP, PLAN) and their structure. Execution HOW is defined by execution-core skill. <example> Context: Creating project plan user: "Create a project plan" assistant: "I'll use project-strategy to structure the BRIEF.md and ROADMAP.md documents." </example> <example> Context: Document format validation user: "Validate this plan structure" assistant: "I'll check against project-strategy format specifications." </example> <example> Context: Template reference user: "Need the BRIEF.md template" assistant: "I'll reference the project-strategy template at assets/templates/brief.md." </example>
/plugin marketplace add Git-Fg/thecattoolkit/plugin install git-fg-builder-plugins-builder@Git-Fg/thecattoolkitThis 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.mdThis 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 trackingFormat 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
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.