athola/project-planning
plugins/attune/skills/project-planning/SKILL.md
Converts a specification into a phased, dependency-ordered implementation plan. Use after specification is complete and before execution begins.
$ install --global
skillsauthnpx skillsauth add athola/claude-night-market project-planningInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 27, 2026, 4:36 AM281.1s1 file scanned
SKILL.md
- name:
- project-planning
- description:
- Converts a specification into a phased, dependency-ordered implementation plan. Use after specification is complete and before execution begins.
- alwaysApply:
- false
- model_preference:
- claude-sonnet-4
- category:
- workflow
- tags:
- [planning, architecture, task-breakdown, dependencies, estimation]
- complexity:
- intermediate
- model_hint:
- standard
- estimated_tokens:
- 900
- role:
- library
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)
Integration
With superpowers:
- Uses
Skill(superpowers:writing-plans)for structured planning - Applies checkpoint-based execution patterns
- Uses dependency analysis framework
Without superpowers:
- Standalone planning methodology
- Task breakdown templates
- Dependency tracking patterns
Quality Checks
Before completing plan:
- ✅ All architecture components documented
- ✅ File Structure section present before tasks
- ✅ All task files appear in File Structure table
- ✅ All FRs mapped to tasks
- ✅ All tasks have acceptance criteria
- ✅ Dependencies are acyclic
- ✅ Effort estimates provided
- ✅ Critical path identified
- ✅ Risks assessed with mitigations
- ✅ Sprints balanced by capacity
Post-Completion: Workflow Continuation (REQUIRED)
Automatic Trigger: After Quality Checks pass and docs/implementation-plan.md is saved, MUST auto-invoke the next phase.
When continuation is invoked:
- Verify
docs/implementation-plan.mdexists and is non-empty - Display checkpoint message to user:
Implementation plan complete. Saved to docs/implementation-plan.md. Proceeding to execution phase... - Invoke next phase:
Skill(attune:project-execution)
Bypass Conditions (ONLY skip continuation if ANY true):
--standaloneflag was provided by the userdocs/implementation-plan.mddoes not exist or is empty (phase failed)- User explicitly requests to stop after planning
Do NOT prompt the user for confirmation — this is a lightweight checkpoint, not an interactive gate. The user can always interrupt if needed.
Related Skills
Skill(superpowers:writing-plans)- Planning methodology (if available)Skill(spec-kit:task-planning)- Task breakdown (if available)Skill(attune:project-specification)- Previous phaseSkill(attune:project-execution)- AUTO-INVOKED next phase after planningSkill(attune:mission-orchestrator)- Full lifecycle orchestration
Related Commands
/attune:blueprint- Invoke this skill/attune:execute- Next step in workflow
Examples
See /attune:blueprint command documentation for complete examples.
Troubleshooting
Common Issues
If you find circular dependencies in your task graph, break one of the tasks into smaller sub-tasks. If sprint capacity is consistently exceeded, re-estimate tasks using the Fibonacci scale or reduce sprint scope.
Related Skills
athola/friction-detector
tools
VerifiedTrustedCommunity
Detect friction signals; graduate patterns into rules. Use for session retrospectives.
300SKILL.mdUpdated Apr 23, 2026
athola/validate-mr
testing
VerifiedTrustedCommunity
Use when you need a diff-derived test plan for an MR — reads the diff, groups changes by area, runs targeted verifications, and proves revert-tests are genuine guards, not dead assertions.
294SKILL.mdUpdated May 30, 2026
athola/palace-index-curator
development
VerifiedTrustedCommunity
Curate the web-capture index. Use when the capture backlog grows, captures sit unprocessed at seedling/pending, or to surface stored research during work.
294SKILL.mdUpdated May 30, 2026
athola/memory-clarity-probe
testing
VerifiedTrustedCommunity
Probe memory/summary clarity via dual anchor questions: task progress, info gaps. Use when verifying session state or summary before handoff or compression.
294SKILL.mdUpdated May 30, 2026