Files
motovaultpro/.claude/skills/planner/SKILL.md
Eric Gullickson 9f00797925
All checks were successful
Deploy to Staging / Build Images (push) Successful in 23s
Deploy to Staging / Deploy to Staging (push) Successful in 36s
Deploy to Staging / Verify Staging (push) Successful in 6s
Deploy to Staging / Notify Staging Ready (push) Successful in 6s
Deploy to Staging / Notify Staging Failure (push) Has been skipped
feat: implement new claude skills and workflow
2026-01-03 11:02:30 -06:00

2.8 KiB

name, description
name description
planner Interactive planning and execution for complex tasks. Use when user asks to use or invoke planner skill.

Planner Skill

Two-phase workflow: planning (create plans) and execution (implement plans).

Invocation Routing

User Intent Script Invocation
"plan", "design", "architect", "break down" planner.py python3 scripts/planner.py --step-number 1 --total-steps 4 --thoughts "..."
"review plan" (after plan written) planner.py python3 scripts/planner.py --phase review --step-number 1 --total-steps 2 ...
"execute", "implement", "run plan" executor.py python3 scripts/executor.py --plan-file PATH --step-number 1 --total-steps 7 ...

Scripts inject step-specific guidance via JIT prompt injection. Invoke the script and follow its REQUIRED ACTIONS output.

When to Use

Use when task has:

  • Multiple milestones with dependencies
  • Architectural decisions requiring documentation
  • Complexity benefiting from forced reflection pauses

Skip when task is:

  • Single-step with obvious implementation
  • Quick fix or minor change
  • Already well-specified by user

Resources

Resource Contents Read When
resources/diff-format.md Unified diff specification for plans Writing code changes in milestones
resources/temporal-contamination.md Comment hygiene detection heuristics Writing comments in code snippets
resources/default-conventions.md Priority hierarchy, structural conventions Making decisions without explicit user guidance
resources/plan-format.md Plan template structure Completing planning phase (injected by script)

Resource loading rule: Scripts will prompt you to read specific resources at decision points. When prompted, read the full resource before proceeding.

Workflow Summary

Planning phase: Steps 1-N explore context, evaluate approaches, refine milestones. Final step writes plan to file. Review phase (TW scrub -> QR validation) follows.

Execution phase: 7 steps -- analyze plan, reconcile existing code, delegate milestones to agents, QR validation, issue resolution, documentation, retrospective.

All procedural details are injected by the scripts. Invoke the appropriate script and follow its output.