Plan
🛠️ Dev Kit — lifecycle-driven Agent Skill for structured development workflows. Brainstorm, plan, implement, debug, fix, test & adversarial code review. Java/Spring Boot + TypeScript/React/Vue rules included. Compatible with Claude Code, Cursor, Kiro, and 40+ agentic clients.
npx -y skills add SoftwareOneHN/dev-kit --skill planAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Plan implementations, design architectures, create technical roadmaps with detailed phases. Use for feature planning, system design, solution architecture, implementation strategy, phase documentation.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
5.9 KB, as published. Nobody here has run it
Planning
Create detailed technical implementation plans through research, codebase analysis, solution design, and comprehensive documentation.
Default (No Arguments)
If invoked with a task description, proceed with planning workflow. If invoked WITHOUT arguments or with unclear intent,
use AskUserQuestion to present available operations:
| Operation | Description |
|---|---|
(default) | Create implementation plan for a task |
archive | Write journal entry & archive plans |
red-team | Adversarial plan review |
validate | Critical questions interview |
Present as options via AskUserQuestion with header "Planning Operation", question "What would you like to do?".
Workflow Modes
Default: --auto (analyze task complexity and auto-pick mode).
| Flag | Mode | Research | Red Team | Validation | Cook Flag |
|---|---|---|---|---|---|
--auto | Auto-detect | Follows mode | Follows mode | Follows mode | Follows mode |
--fast | Fast | Skip | Skip | Skip | --auto |
--hard | Hard | 2 researchers | Yes | Optional | (none) |
--parallel | Parallel | 2 researchers | Yes | Optional | --parallel |
--two | Two approaches | 2+ researchers | After selection | After selection | (none) |
Add --no-tasks to skip task hydration in any mode.
Load: references/workflow-modes.md for auto-detection logic, per-mode workflows, context reminders.
When to Use
- Planning new feature implementations
- Architecting system designs
- Evaluating technical approaches
- Creating implementation roadmaps
- Breaking down complex requirements
Core Responsibilities & Rules
Always honoring YAGNI, KISS, and DRY principles. Be honest, be brutal, straight to the point, and be concise.
1. Research & Analysis
Load: references/research-phase.md
Skip if: Fast mode or provided with researcher reports
2. Codebase Understanding
Load: references/codebase-understanding.md
Skip if: Provided with scout reports
3. Solution Design
Load: references/solution-design.md
4. Plan Creation & Organization
Load: references/plan-organization.md
5. Task Breakdown & Output Standards
Load: references/output-standards.md
Workflow Process
- Pre-Creation Check → Check Plan Context for active/suggested/none
- Mode Detection → Auto-detect or use explicit flag (see
workflow-modes.md) - Research Phase → Spawn researchers (skip in fast mode)
- Codebase Analysis → Read docs, scout if needed
- Plan Documentation → Write comprehensive plan via planner subagent
- Red Team Review → Use
Skilltool:plan:red-team {plan-path}(hard/parallel/two modes) - Post-Plan Validation → Use
Skilltool:plan:validate {plan-path}(hard/parallel/two modes) - Hydrate Tasks → Create Claude Tasks from phases (default on,
--no-tasksto skip) - Context Reminder → Output cook command with absolute path (MANDATORY)
Output Requirements
- DO NOT implement code - only create plans
- Respond with plan file path and summary
- Ensure self-contained plans with necessary context
- Include code snippets/pseudocode when clarifying
- Fully respect the
./docs/development-rules.mdfile
Task Management
Plan files = persistent. Tasks = session-scoped. Hydration bridges the gap.
Default: Auto-hydrate tasks after plan files are written. Skip with --no-tasks.
3-Task Rule: <3 phases → skip task creation.
Load: references/task-management.md for hydration pattern, TaskCreate patterns, cook handoff protocol.
Hydration Workflow
- Write plan.md + phase files (persistent layer)
- TaskCreate per phase with
addBlockedBychain - TaskCreate for critical/high-risk steps within phases
- Metadata: phase, priority, effort, planDir, phaseFile
- Cook picks up via TaskList (same session) or re-hydrates (new session)
Active Plan State
Check ## Plan Context injected by hooks:
- "Plan: {path}" → Active plan. Ask "Continue? [Y/n]"
- "Suggested: {path}" → Branch hint only. Ask if activate or create new.
- "Plan: none" → Create new using
Plan dir:from## Naming
After creating plan: node .claude/scripts/set-active-plan.cjs {plan-dir}
Reports: Active plans → plan-specific path. Suggested → default path.
Important
DO NOT create plans or reports in USER directory. ALWAYS create plans or reports in CURRENT WORKING PROJECT DIRECTORY.
Subcommands
| Subcommand | Reference | Purpose |
|---|---|---|
/plan archive | references/archive-workflow.md | Archive plans + write journal entries |
/plan red-team | references/red-team-workflow.md | Adversarial plan review with hostile reviewers |
/plan validate | references/validate-workflow.md | Validate plan with critical questions interview |
Quality Standards
- Thorough and specific, consider long-term maintainability
- Research thoroughly when uncertain
- Address security and performance concerns
- Detailed enough for junior developers
- Validate against existing codebase patterns
Remember: Plan quality determines implementation success. Be comprehensive and consider all solution aspects.