spec-author
From the author
Write an executable specification under docs/graph/specs/ that turns a clear goal into testable contracts. Use whenever a feature, endpoint, job, significant function, or AI interaction needs a contract that the tester can encode and the implementer can satisfy. Coordinates product (§3, §9), architect (§4, §6, §7), and tester (§10 testability review) into a single signed-off document. Specs are the source of truth for behavior (`rule.spec`).
Install
npx skills add llopresto87/Cypress --skill spec-author -a claude-code
Installs to .claude/skills/spec-author/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- spec-writingjeremylongshore/tons-of-skills-marketplaceExecute this skill should be used when the user asks about "writing specs", "specs.md format", "how to write specifications", "sprint requirements", "testing configuration", "scope definition", or needs guidance on creating effective sprint specifications for agentic development. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.Writing★ 2.9K
- spec-extractarcasilesgroup/ai-engineeringTurn an unwritten agreement into a checkable spec — pull the requirements out of this conversation, a ticket, a pasted thread, or a design discussion, and write them to the project's spec file as numbered, falsifiable claims. Use before starting a feature, when the user says "write this up", "turn this into a spec", "make a design doc", "what did we agree", "capture the requirements", or "create design.md"; when a review skill halts because no spec exists; and at the point a conversation has produced enough decisions that the next session would lose them. This produces the contract that `design-check` and `verify-feature` measure against — it does not verify anything itself.Planning★ 61
- idea-to-specDevelopersGlobal/ai-agent-skillsConverts vague ideas into concrete, testable specifications with acceptance criteria. No implementation begins without a spec.Planning★ 215
- implementation-planningcbrock84/headcountTurns a spec or requirement into a written plan a separate session or agent can execute, then drives that plan through review checkpoints. Use this before touching code on any multi-step task, when work needs handing to someone else, when a task keeps sprawling mid-implementation, or when a plan exists and needs executing in order with verification between steps.Planning★ 2.1K
- spec-creationa5c-ai/babysitterFeature specification creation from codebase research. Produces requirements, acceptance criteria, architecture decisions, implementation plans, and risk analysis.Planning★ 1.9K
- feature-specw95/awesome-claude-corporate-skillsWrite detailed feature specifications with functional requirements, edge cases, data models, API contracts, and UX flows. Create comprehensive technical specifications that enable clear implementation.Planning★ 276
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in