Menu

Individual skill

dev-spec

Compatibility alias for dev-grill-docs spec-only mode. Use for explicit dev-spec requests, old dev-spec workflows, or spec-only output without CONTEXT.md / ADR updates. Ordinary requirement alignment belongs to dev-grill-docs. Preserves the feature artifact and acceptance contract, including when installed standalone.

plugins/Jason-chen-coder/dev-skills/skills/dev-spec/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,531
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 Spec

Treat `dev-spec` as `dev-grill-docs --spec-only`, forwarding `--quick` or `--deep`. Read [references/dev-baseline.md](references/dev-baseline.md).

When `dev-grill-docs` is available in the installed skill catalog, load it and apply its spec-only mode. Do not assume a sibling directory exists. When it is unavailable, use the compact compatibility contract below; no other skill is required to produce the artifact.

## Standalone compatibility contract

- Read the user's request and relevant existing docs, code, terminology, and tests before asking questions.
- Ask only about material unresolved behavior, scope, or acceptance. Preserve prior decisions; a clear request needs no mandatory interview. Record consequential evidence-backed assumptions and keep high-impact unresolved decisions explicit.
- Produce `.claude/artifacts/designs/<feature>.md` in the user's project unless the user specifies another path or chat-only output. Reuse an identifiable existing slug; otherwise choose a descriptive one without a routine confirmation turn.
- Include `Background`, `In scope`, `Out of scope`, `Solution`, and observable `Acceptance criteria` with stable `AC-1` identifiers. Include `Assumptions`, `Edge cases & risks`, `Open questions`, and core entities where relevant. The solution is a behavior sketch, not an implementation task list.
- Record source and update date. Preserve status vocabulary: `DRAFT` for proposed or unaligned intent, `ALIGNED` for materially resolved requirements supported by user direction or an accepted source, `STUCK` for concrete blocking questions, and `IMPLEMENTED` only when actual implementation evidence supports it. Changed requirements invalidate implementation status for the affected scope.
- A `STUCK` contract identifies the blocking decision, affected scope, and needed evidence or owner. Do not advance dependent implementation or planning by treating file existence as readiness.