04 Spec
Generate or refine a project spec from a free-form human request, an existing PRD, or reviewer findings. Use when the user says "draft spec", "spec for X", "refine the spec", "generate spec from prd", "/spec", or when an orchestrator needs a normalized contract before planning. Do NOT use for writing source code, drafting a full PRD, or modifying a validated and locked spec.
Install
$ agentstack add skill-ai-driven-dev-framework-04-spec ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-ai-driven-dev-framework-04-spec) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Spec
Generates or refines the immutable contract between human intent and downstream agents.
Available actions
| # | Action | Role | Input | | --- | --------- | ----------------------------------------------------------------- | -------------------------------------- | | 01 | build | Create a fresh spec from a free-form request or an existing PRD | request or prdpath, featurename | | 02 | refine | Rewrite an existing spec to address reviewer findings | existing_spec, findings |
Default flow
Non-sequential. The router dispatches based on inputs:
existing_specandfindingspresent ->refinerequestorprd_pathpresent ->build
Transversal rules
- Never invent missing information. Mark every gap as
TBD:instead of guessing. - If the request is too vague to draft a useful spec, return early and ask the user to brainstorm the request first; do not fabricate intent.
- Never modify a spec that has been validated and locked.
- The spec is the contract; it is immutable once validated.
- Keep the spec readable: clear section headers, bulleted criteria, explicit non-goals.
- Never include implementation detail (libraries, patterns, file layout); those belong to the plan.
- Do not self-validate. The caller spawns a reviewer with
@assets/spec-validator.yml; findings come back through therefineaction for the next iteration.
References
- None.
Assets
@assets/spec-template.md: canonical structure of a spec.@assets/spec-validator.yml: checklist used by the reviewer to validate a spec.
External data
- None.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ai-driven-dev
- Source: ai-driven-dev/framework
- License: MIT
- Homepage: https://www.ai-driven-dev.fr/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.