project-planning
Originally fromjezweb/claude-skills
Installation
SKILL.md
Delegation
For detailed task planning workflows, this skill delegates to spec-kit:task-planning as the canonical implementation. Use this skill for quick planning needs; use spec-kit for comprehensive project plans.
When To Use
- After specification phase completes
- Need to design system architecture
- Need task breakdown for implementation
- Planning sprints and resource allocation
- Converting requirements into actionable tasks
- Defining component interfaces and dependencies
When NOT To Use
- No specification exists yet (use
Skill(attune:project-specification)first) - Still exploring problem space (use
Skill(attune:project-brainstorming)instead) - Ready to execute existing plan (use
Skill(attune:project-execution)instead) - Need to adjust running project (update plan incrementally, don't restart)
Related skills
More from athola/claude-night-market
code-quality-principles
KISS, YAGNI, and SOLID code quality principles for clean code, reducing complexity and preventing over-engineering.
94project-brainstorming
Guide project ideation via Socratic questioning to generate project briefs.
92doc-generator
Generate or remediate documentation with human-quality writing and style.
81rigorous-reasoning
Anti-sycophancy reasoning checklist.
79project-specification
Transform project briefs into testable specifications with user stories, acceptance criteria, and measurable outcomes.
78bloat-detector
Detect codebase bloat via progressive analysis: dead code, duplication, complexity, and doc bloat.
71