dvy1987/agent-loom / .agents/skills/feature-spec
feature-spec
VerifiedWrite the executable feature specification — the WHAT and WHY artifact that agents and reviewers treat as source of truth. Owns both /specify and /clarify modes. Load when the user asks to write a feature spec, write a specification, write an executable spec, define functional requirements, capture acceptance criteria as Given/When/Then, or when the spec-driven-development orchestrator routes here. Also triggers on "feature spec", "executable spec", "/specify", "/clarify", "write the spec for this feature", "specification for", "spec-driven", "machine-readable spec". Output: docs/specs/YYYY-MM-DD-<slug>-feature-spec.md. Hard gate: cannot Approve while [NEEDS CLARIFICATION] markers remain.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.5 KB |
| references/examples.md | markdown | 1.3 KB |
| references/feature-spec-schema.md | markdown | 4.9 KB |
references/examples.md
View on GitHub# Feature Spec — Full Worked Examples
Source: addyosmani/agent-skills `spec-driven-development` spec patterns (2026-05-29 snapshot). Security-scanned SAFE.
---
## Example 1 — Assumptions block before draft
**Input:** "Spec out dark mode"
```markdown
## Assumptions I'm Making
- Users toggle in settings (not system-only) — **confirm?**
- Scope: web app only, not marketing site
- Existing design tokens in DESIGN.md are source of truth
- Out of scope: per-component overrides
→ User confirms or corrects before FR/NFR draft.
```
---
## Example 2 — Vague requirement reframe
**Input:** "Make it fast and intuitive"
**Reframe:**
- "Fast" → NFR: LCP < 2.5s on 4G (measurable)
- "Intuitive" → FR: user completes primary flow in ≤3 clicks without help doc
---
## Example 3 — Given/When/Then acceptance criteria
**FR-3:** User can enable dark mode
```gherkin
Given the user is on Settings
When they toggle "Dark mode"
Then the UI uses dark tokens and preference persists across reload
And contrast meets APCA thresholds per design-system
```
---
## Example 4 — Clarify mode output
**Input:** `/clarify` on draft spec
```markdown
Open clarifications (max 3):
1. Persist preference per-device or per-account?
2. Default: system preference or light?
3. Email templates included in scope?
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |