Menu

Individual skill

dev-plan

Create a concrete implementation plan from a spec or clearly scoped request before coding. Use for implementation-planning requests such as 出个 plan, 技术实施方案, plan this, or consensus plan. Ground steps in the repository and scale tradeoff analysis and independent review to risk. Clarify material requirement gaps when needed; do not force an intake workflow for already clear scope. Supports --quick and --deliberate.

plugins/Jason-chen-coder/dev-skills/skills/dev-plan/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,533
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Dev Plan

Produce an implementable, verifiable plan within the user's stated scope. Planning does not authorize implementation. Read [references/dev-baseline.md](references/dev-baseline.md).

## Establish the contract

Read the supplied spec or related `.claude/artifacts/designs/<feature>.md`, relevant code, existing tests, and any accepted ADR. Preserve source links, acceptance criterion identifiers, scope exclusions, assumptions, and open questions. A clear request is sufficient without a separate spec artifact; summarize its requirements in the plan.

If a missing requirement materially changes the solution, ask for that decision or explain the blocked portion. Use `dev-grill-docs` when the task actually requires broader requirement alignment and that skill is available. Continue planning independent parts. Do not require a new intake invocation merely because a spec file is absent. A `STUCK` source must have its blocking questions resolved before planning dependent implementation.

Inspect actual definitions and call paths before naming modification targets. New paths must be labeled proposed. Cite existing paths and symbols; use line numbers only when verified and helpful. Do not manufacture precision or require a percentage of steps to contain line numbers.

## Scale planning to risk