Skip to main content
Generalhashgraph-online

dev-spec

Use when the user has a fuzzy or under-specified feature request and wants to align on what to build before coding. Trigger on: 帮我设计, 写个方案, 这个需求要怎么做, spec 一下, 设计文档, design this, scope this out. Surfaces ambiguities first, asks before choosing among interpretations, and produces a structured spec with scope, solution sketch, risks, and verifiable acceptance criteria. Does not write code, plan implementation, fix bugs, or review commits.

Stars
336
Source
hashgraph-online/awesome-codex-plugins
Updated
2026-05-27
Slug
hashgraph-online--awesome-codex-plugins--dev-spec
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/hashgraph-online/awesome-codex-plugins/HEAD/plugins/Jason-chen-coder/dev-skills/skills/dev-spec/SKILL.md -o .claude/skills/dev-spec.md

Drops the SKILL.md into .claude/skills/dev-spec.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

Dev Spec

dev-spec is a compatibility alias for dev-grill-docs --spec-only.

Use it when the user explicitly asks for dev-spec, wants old dev-spec compatibility, or explicitly asks for spec-only output without CONTEXT.md / ADR writes. For ordinary requirement alignment, prefer dev-grill-docs. Do not run a separate interview protocol from this file.

Trigger routing

Trigger phrases include:

  • dev-spec
  • 旧 dev-spec 流程
  • dev-spec --spec-only
  • 只要 spec
  • spec-only

Do not capture these generic requirement-intake phrases here; route them to dev-grill-docs:

  • spec 一下
  • 设计文档
  • 帮我设计
  • 写个方案
  • 这个需求要怎么做
  • design this
  • scope this out

Behavior:

  1. Load ../dev-grill-docs/SKILL.md.
  2. Follow the dev-grill-docs workflow with --spec-only.
  3. Produce .claude/artifacts/designs/<feature>.md.
  4. Do not update CONTEXT.md or docs/adr/ unless the user explicitly asks to update persistent docs too.

Output goes to .claude/artifacts/designs/<feature>.md.

Optional arguments are forwarded:

  • --quick
  • --deep
  • default mid-depth mode

Compatibility contract

Existing downstream tools may still refer to dev-spec. Keep these semantics stable:

  • The artifact path remains .claude/artifacts/designs/<feature>.md.
  • The artifact status remains DRAFT | ALIGNED | IMPLEMENTED | STUCK.
  • STUCK still means open questions block dev-plan.
  • Acceptance criteria remain the source consumed by dev-plan, dev-tdd, dev-verify, and dev-code-review.
  • dev-auto, old docs, and old prompts may continue to say dev-spec; treat that as dev-grill-docs --spec-only.

Hard rules

  • Do not copy or fork the grill/spec workflow here.
  • Do not update CONTEXT.md / ADR from this alias unless explicitly requested.
  • Do not write code.
  • Do not route bugs here; use dev-fix.

Multi-Agent Note

dev-spec remains main-agent-first because it negotiates scope with the user, but the actual workflow lives in dev-grill-docs.

Explorers may gather bounded read-only context. Apply ../../docs/multi-agent-policy.md for delegation boundaries.

SDD Contract

dev-spec remains a stable compatibility name for the feature intent contract.

When invoked, the contract is produced by dev-grill-docs --spec-only and has the same downstream anchors:

  • In scope
  • Out of scope
  • Assumptions
  • Open questions
  • Acceptance criteria