AsiaOstrichAsiaOstrich/EngramGraph/.agents/skills/spec-derivation/SKILL.md

spec-derive

Skill4 starsChanged 29 days agoMITView on GitHub

[UDS] Derive BDD scenarios, TDD skeletons, integration and E2E tests, and ATDD tables from an approved specification. Use when: a spec has been approved and needs test artifacts, generating tagged test skeletons from acceptance criteria, producing contract stubs from a spec. Not for: recovering a spec from existing code — use /reverse; writing or reviewing the spec itself — use /sdd. Keywords: forward derivation, spec to test, BDD scenario, TDD skeleton, ATDD table, 正向推演, 規格衍生, 測試生成.

1 other project uses a version of this.

Adopted by

Most recently taken up by

AsiaOstrich/universal-dev-standardsword for word, first seen Nov 4, 2026

Other versions1 project uses a version of this.
Word for word · 1
AsiaOstrich/universal-dev-standards★ 84100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository55 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ac-coverageSkill
- adrSkill
- ai-collaboration-standardsSkill
- ai-friendly-architectureSkill
- ai-instruction-standardsSkill
- api-designSkill
- atddSkill
- auditSkill
- bddSkill
- brainstormSkill
- changelogSkill
- checkinSkill
- ci-cdSkill
- code-reviewSkill
- commitSkill
- contract-testSkill
- databaseSkill
- deploySkill
- methodologySkill
- dev-workflowSkill
- docgenSkill
- documentation-guideSkill
- durableSkill
- e2eSkill
- error-code-guideSkill
- git-workflow-guideSkill
- incidentSkill
- journey-test-assistantSkill
- knowledge-graphSkill
- logging-guideSkill
- metricsSkill
- migrateSkill
- observabilitySkill
- orchestrateSkill
- planSkill
- prSkill
- discoverSkill
- project-structure-guideSkill
- pushSkill
- refactorSkill
- releaseSkill
- requirementSkill
- retrospectiveSkill
- reverseSkill
- runbookSkill
- securitySkill
- scanSkill
- skill-builderSkill
- sloSkill
- sddSkill
- sweepSkill
- tddSkill
- coverageSkill
- testing-guideSkill

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Generate Artifacts: - Create BDD/TDD/ATDD outputs | 產生衍生工件
line 59
Distinctive:
Verify: - Ensure 1:1 mapping between AC and generated items | 驗證一對一對應
line 60
Very specific:
After /derive completes, the AI assistant should suggest:
line 92

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Forward Derivation | 正向推演

Generate derived artifacts (BDD scenarios, TDD skeletons, ATDD tables) from approved SDD specifications.

從已批准的 SDD 規格生成衍生工件（BDD 場景、TDD 骨架、ATDD 表格）。

Subcommands | 子命令

Subcommand	Description	Output
`all`	Full derivation pipeline (BDD + TDD + IT + E2E + ATDD + Contracts)	`.feature` + `.test.` + `.it.test.` + `.e2e.test.*` + `.md` + `.json`
`bdd`	Generate BDD scenarios only	`.feature`
`tdd`	Generate TDD skeletons only	`.test.*`
`it`	Generate Integration test skeletons	`.it.test.*`
`e2e`	Generate E2E test skeletons	`.e2e.test.*`
`atdd`	Generate ATDD test tables	`.md` (Markdown tables)

Workflow | 工作流程

Read Spec - Analyze the input SPEC-XXX.md file | 分析規格檔案
Extract AC - Parse all Acceptance Criteria | 解析所有驗收條件
Generate Artifacts - Create BDD/TDD/ATDD outputs | 產生衍生工件
Verify - Ensure 1:1 mapping between AC and generated items | 驗證一對一對應

Anti-Hallucination Rules | 防幻覺規則

Rule	Description	說明
1:1 Mapping	Every AC has exactly one test/scenario	每個 AC 對應一個測試
Traceability	All artifacts reference Spec ID and AC ID	所有工件引用規格與 AC 編號
No Invention	Do not add scenarios not in the spec	不新增規格外的場景

Generated Artifact Tags | 產生工件標籤

Tag	Meaning	含義
`[Source]`	Direct content from spec	直接來自規格
`[Derived]`	Transformed from source	從來源轉換
`[Generated]`	AI-generated structure	AI 產生的結構
`[TODO]`	Requires human implementation	需人工實作

Usage | 使用方式

/derive all specs/SPEC-001.md           - Full derivation pipeline | 完整推演管線
/derive bdd specs/SPEC-001.md           - Derive BDD scenarios only | 僅推演 BDD 場景
/derive tdd specs/SPEC-001.md           - Derive TDD skeletons only | 僅推演 TDD 骨架
/derive it specs/SPEC-001.md            - Derive Integration test skeletons | 推演整合測試骨架
/derive e2e specs/SPEC-001.md           - Derive E2E test skeletons | 推演 E2E 測試骨架
/derive atdd specs/SPEC-001.md          - Derive ATDD tables | 推演 ATDD 表格

Next Steps Guidance | 下一步引導

After /derive completes, the AI assistant should suggest:

測試工件已產生。建議下一步 / Test artifacts generated. Suggested next steps:
執行 /tdd 開始紅綠重構循環 ⭐ Recommended / 推薦 — Start Red-Green-Refactor cycle
執行 /bdd 細化 Gherkin 場景 — Refine Gherkin scenarios
檢查產生的 [TODO] 標記並補齊實作 — Review [TODO] markers and fill in implementations

Reference | 參考

Detailed guide: guide.md
Core standard: forward-derivation-standards.md

AI Agent Behavior | AI 代理行為

完整的 AI 行為定義請參閱對應的命令文件：/derive
For complete AI agent behavior definition, see the corresponding command file: /derive

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free