Plan new

Skill GrinRus/ai_driven_dev/skills/plan-new

Drafts implementation plan from ready PRD and research artifacts. Use when PRD and research gates pass and plan stage should start. Do not use when the request is feature kickoff in `idea-new` or readiness approval in `review-spec`.From its SKILL.md

Install

npx -y skills add GrinRus/ai_driven_dev --skill plan-new

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

5 stars5 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.

SKILL.md

3.4 KB, as published. Nobody here has run it

Follow feature-dev-aidd:aidd-core.

Steps

Set active stage plan and active feature.
Run python3 ${CLAUDE_PLUGIN_ROOT}/skills/plan-new/runtime/research_check.py --ticket <ticket>.
Gate readiness with python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/prd_check.py and python3 ${CLAUDE_PLUGIN_ROOT}/skills/plan-new/runtime/research_check.py; block early if either fails.
Use the existing rolling context pack as input evidence; do not invoke standalone context-pack builder scripts from this stage.
Runtime-path safety: execute only canonical runtime commands from this contract (python3 ${CLAUDE_PLUGIN_ROOT}/skills/.../runtime/...).
Root-relative /skills/... runtime paths are forbidden; use only ${CLAUDE_PLUGIN_ROOT}/skills/.../runtime/....
Run subagent feature-dev-aidd:planner. The planner is the only writer for aidd/docs/plan/<ticket>.md.
Run subagent feature-dev-aidd:validator. The validator is read-only and returns the narrative verdict and gap list only.
Final stage readiness is sourced from prd_check + research_check + validator verdict; return /feature-dev-aidd:review-spec <ticket> only on the ready path.
Otherwise return PENDING or BLOCKED with the validator gaps and the canonical next action for the current stage.

Command contracts

`python3 ${CLAUDE_PLUGIN_ROOT}/skills/plan-new/runtime/research_check.py`

When to run: before planning to enforce research-readiness gate.
Inputs: --ticket <ticket> and current PRD/research artifacts.
Outputs: deterministic readiness verdict for plan stage.
Failure mode: non-zero exit if research status/artifacts do not satisfy gate policy.
Next action: resolve research blockers and rerun the gate check.

`python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/prd_check.py`

When to run: before planner execution and before final stage verdict normalization.
Inputs: active PRD artifacts for the current ticket.
Outputs: deterministic PRD readiness verdict used by the stage command as source-of-truth input.
Failure mode: non-zero exit when required PRD fields or readiness markers are missing.
Next action: fix the PRD blockers, then rerun the gate before planning continues.

Notes

Planning stage: AIDD:ACTIONS_LOG: n/a.

Additional resources

Plan template source: templates/plan.template.md (when: generating or normalizing plan structure; why: ensure planner/validator outputs follow canonical sections).