Project planning standards, templates, execution protocols, verification standards, and handoff procedures for BRIEF.md, ROADMAP.md, PLAN.md, phase execution, verification points, and authentication gates. <example> Context: User wants to create a project plan user: "Create a project plan for our new feature" assistant: "I'll load the project-lifecycle skill to create BRIEF.md and ROADMAP.md." </example> <example> Context: User needs to execute a phase user: "Execute phase 1 of our plan" assistant: "I'll use the project-lifecycle skill to understand phase execution standards." </example> <example> Context: Handling authentication gates user: "The deployment failed with auth error" assistant: "I'll load the project-lifecycle skill to handle the authentication gate properly." </example>
/plugin marketplace add Git-Fg/thecattoolkit/plugin install git-fg-cat-toolkit-planner-plugins-planner@Git-Fg/thecattoolkitThis skill is limited to using the following tools:
assets/templates/adr-entry.mdassets/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/adr-format.mdreferences/authentication-gates.mdreferences/context-management.mdreferences/dependency-management.mdreferences/execution-observation-points.mdreferences/git-integration.mdreferences/issues-format.mdreferences/phase-patterns.mdreferences/plan-format.mdreferences/scope-estimation.mdTemplates and Resources:
assets/templates/references/Reference Resources:
assets/templates/ - Document templates for all project lifecycle phasesreferences/plan-format.md - PLAN.md structure guidelinesreferences/phase-patterns.md - Phase breakdown patternsreferences/scope-estimation.md - Task complexity estimationreferences/context-management.md - Context management practicesreferences/execution-observation-points.md - Verification point standardsreferences/authentication-gates.md - Authentication error handlingreferences/git-integration.md - Git integration standardsreferences/ - All planning and execution protocol standards| Document Type | Template Location | Use Case |
|---|---|---|
| Project Brief | assets/templates/brief.md | Project starts |
| Roadmap | assets/templates/roadmap.md | Multi-phase projects |
| Phase Plan | assets/templates/phase-plan.md | Executable phases |
| Issue Entry | assets/templates/issue-entry.md | Deferred enhancements |
| Issues File | assets/templates/issues.md | ISSUES.md creation |
| Phase Summary | assets/templates/summary.md | Phase completions |
| Session Handoff | assets/templates/handoff.md | Session pauses mid-phase |
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
domain: [optional]
status: in_progress
---
Valid Status Values: in_progress, completed
Structure Reference: See references/plan-format.md for detailed PLAN.md structure guidelines.
Standard Sections:
Git Integration Standards
Reference: See references/git-integration.md for git integration guidelines.
Standard Commit Points:
Standard Commit Format:
feat(domain): [one-liner from SUMMARY.md]
- [Key accomplishment 1]
- [Key accomplishment 2]
- [Key accomplishment 3]
Commit Pattern: Separate commits for PLAN.md creation, RESEARCH.md, FINDINGS.md, or minor planning tweaks are not part of the standard workflow.
Reference: See references/execution-observation-points.md for verification point guidelines.
Self-Verification Points replace Blocking Checkpoints:
Standard Practice: Automated verification is preferred over manual intervention when possible.
Reference: See references/authentication-gates.md for authentication error handling.
Standard Response to Auth Errors:
Planning Document Compliance:
BRIEF.md Compliance:
ROADMAP.md Compliance:
PLAN.md Compliance:
Execution Document Compliance:
SUMMARY.md Compliance:
HANDOFF.md Compliance:
These examples demonstrate the correct Handoff Reason for various scenarios.
<input> CLI returns "Error: Login required to deploy" </input> <reason>AUTH_GATE</reason> <action>Create HANDOFF.md requesting credentials.</action> <input> Task requires "Create User Model" but no database technology is selected in BRIEF.md </input> <reason>AMBIGUOUS</reason> <action>Create HANDOFF.md requesting architectural decision.</action> <input> Git push rejected with "Updates were rejected" </input> <reason>CONFLICT</reason> <action>Create HANDOFF.md requesting merge resolution.</action>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.