docs-spec-system

Category: Tools & Productivity | Uploader: dana0550 | Downloads: 0 | Version: v1.0（Latest）

Operate the Spec System v2 contract-first workflow with phase gates, EARS+RFC requirements, Gherkin scenarios, strict traceability, and first-class specctl enforcement.

Changelog: Source: GitHub https://github.com/dana0550/spec-system

Directory Structure

Current level: skills/docs-spec-system/

📁 .claude-plugin/
- 📄 plugin.json 339 B
📁 agents/
- 📄 openai.yaml 330 B
📁 assets/
- 📁 templates/
  - 📄 BUGFIX_SPEC_TEMPLATE.md 528 B
  - 📄 EPIC_BRIEF_TEMPLATE.md 353 B
  - 📄 EPIC_DECOMPOSITION_TEMPLATE.yaml 532 B
  - 📄 EPIC_ONESHOT_TEMPLATE.yaml 1010 B
  - 📄 FEATURE_DESIGN_TEMPLATE.md 272 B
  - 📄 FEATURE_REQUIREMENTS_TEMPLATE.md 544 B
  - 📄 FEATURE_TASKS_TEMPLATE.md 361 B
  - 📄 FEATURE_VERIFICATION_TEMPLATE.md 243 B
  - 📄 ONESHOT_BLOCKER_LEDGER_TEMPLATE.md 356 B
  - 📄 STEERING_TEMPLATE.md 189 B
- 📄 docs-system-pr-template.md 1.3 KB
📁 references/
- 📄 release-and-pr.md 1.9 KB
- 📄 spec-system-rules.md 5.6 KB
- 📄 workflows.md 5.4 KB
📁 skills/
- 📁 spec-system/
  - 📄 SKILL.md 1.9 KB
📄 SKILL.md 2.1 KB

SKILL.md

---
name: docs-spec-system
description: Operate the Spec System v2 contract-first workflow with phase gates, EARS+RFC requirements, Gherkin scenarios, strict traceability, and first-class specctl enforcement.
---

# Docs Spec System v2

Run all docs-spec operations through the phase-gated v2.4 system.

## Runbook

1. Read `references/spec-system-rules.md` for mandatory schemas and gate invariants.
2. Select the workflow in `references/workflows.md` that matches the requested change.
3. Use `specctl` as the primary interface (`feature`, `epic`, `oneshot`, `impact`, `codex`, `lint`, `render`, `check`, `approve`, `report`).
4. Keep requirements, design, tasks, and verification artifacts synchronized per feature.
5. Enforce `R -> D -> T -> S -> evidence` traceability before completion.
6. For epic work, enforce one-shot contract execution (`run -> check -> finalize`) with blockers/memory artifacts.
7. Use `references/release-and-pr.md` and `assets/docs-system-pr-template.md` to assemble release/PR outputs.

## Required Output For Every Task

- List impacted IDs by type (`E`, `F`, `R`, `D`, `T`, `S`) and operation type.
- Report phase transitions performed (if any).
- Report `specctl check` result and blocking errors/warnings.
- Report impact status (`specctl impact scan`) and any open suspects.
- For one-shot runs, report run ID, checkpoint results, blocker count, and finalize status.
- For agentic epic work, report runner policy, question/approval outcomes, and key artifact paths.

## Out-of-Scope Handling

- Do not infer implementation status from source code without explicit evidence.
- Do not run legacy v1 script workflows.
- Do not bypass phase gates unless the user explicitly requests a policy exception.
- Do not finalize one-shot runs with unresolved blocker ledger entries or placeholder markers.

## Skill Resources

- `references/spec-system-rules.md`: v2 schema, ID grammar, and quality gate rules.
- `references/workflows.md`: phase-driven execution playbooks.
- `references/release-and-pr.md`: PR assembly and release validation.
- `assets/docs-system-pr-template.md`: v2 PR template.
- `assets/templates/*.md`: canonical feature and governance templates.

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

docs-spec-system

Directory Structure

SKILL.md

Report

Notice