Generate phased, dependency-annotated implementation plans from approved specs.
npx skills add https://github.com/smartmarbles/helm --skill create-plan-smartmarbles
Please help me install this Agent Skill. Skill: create-plan Source: https://github.com/smartmarbles/helm/tree/main/.github/skills/create-plan Command: npx skills add https://github.com/smartmarbles/helm --skill create-plan-smartmarbles
Implementation-plan authoring playbook for SAGE — the how-to for turning an approved spec (or a clear standard-path request) into a phased, dependency-annotated plan an implementer can execute without further clarification. Use this skill whenever SAGE is asked to produce a plan, whenever ARTHUR routes work down the standard path, whenever a spec has been approved at the Spec Checkpoint, whenever work must be decomposed into phases with PARALLEL / BLOCKED BY / Depends on annotations, or whenever a multi-file or multi-agent effort needs explicit file-ownership and sequencing before dispatch. NOT for: writing feature specifications (use this skill create-spec), research-only requests (route to SCOOP), code or documentation implementation (SAGE does not implement), or identity/persona questions about SAGE (those live in the agent file).
High-intent search queries and answers about installing and using this skill.
To turn an approved spec into a phased implementation plan, you generate a dependency-annotated document specifying execution phases, per-task dependencies, and file ownership. This ensures the resulting Plan Checkpoint artifact can be executed without further clarification.
Sequencing multi-file tasks with parallel and blocked dependencies is best handled by decomposing the effort into explicit phases with PARALLEL, BLOCKED BY, and Depends on annotations. This guarantees clear file ownership and correct execution order before dispatch.
You need a dependency-annotated plan for multi-agent efforts whenever work requires explicit sequencing and file ownership before dispatch. Generating a phased plan with per-task dependencies ensures agents execute their assigned files without conflict.
No, you cannot use this planning skill to write feature specifications. It is designed exclusively for generating phased plans from approved specs, not for writing the initial feature specifications themselves.
Yes, the planning skill supports writing the plan artifact directly to disk. It generates a Plan Checkpoint artifact on disk via create_file, ensuring the dependency-annotated phased plan is persisted for downstream execution.
You should not use an implementation plan for research-only requests because this skill specifically decomposes approved specs into executable phases. Research-only requests should be routed to a different process, as this skill does not handle research or code implementation.
arbiterForgeConvert approved specifications into executable implementation plans with ordered tasks.
truongnatExecute approved plans with adaptive replanning and dependency-aware task sequencing.
warpdotdevPlan and execute feature implementations while keeping specs aligned with code changes.
cslsoftwaresRoute workspace consolidation requests to specialized audit skills.
