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.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- dev-spec
- description
- 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.
02 资源文件 2
- 参考文档examples.md1.4 KB
- 参考文档references/dev-baseline.md3.5 KB
03 SKILL.md 正文
Dev Spec
Treat dev-spec as dev-grill-docs --spec-only, forwarding --quick or --deep. Read 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>.mdin 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 observableAcceptance criteriawith stableAC-1identifiers. IncludeAssumptions,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:
DRAFTfor proposed or unaligned intent,ALIGNEDfor materially resolved requirements supported by user direction or an accepted source,STUCKfor concrete blocking questions, andIMPLEMENTEDonly when actual implementation evidence supports it. Changed requirements invalidate implementation status for the affected scope. - A
STUCKcontract identifies the blocking decision, affected scope, and needed evidence or owner. Do not advance dependent implementation or planning by treating file existence as readiness. - Report the artifact and unresolved issues. Respect intake-only or analysis-only scope. If broader implementation is already authorized, continue through the available workflow when requirements are sufficient.
Boundaries
This alias writes no CONTEXT.md or docs/adr/ unless the user explicitly adds those outputs. It does not implement code or diagnose bugs. Analysis-only and no-file instructions take precedence over the default artifact path. See examples.md for compatibility cases.
SDD Contract
Preserve In scope, Out of scope, Assumptions, Open questions, and stable Acceptance criteria for downstream planning, implementation, verification, and review. Existing calls to dev-spec keep the same artifact path and lifecycle vocabulary as dev-grill-docs --spec-only.
Multi-Agent Note
Main-agent-first. If delegation is available and authorized, explorers may gather bounded facts and independent reviewers may evaluate a substantial contract; one agent owns questions and writes. In the source repository, docs/multi-agent-policy.md provides optional guidance, not a dependency for standalone use.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.