A spec-first workflow for coderX agents that processes requirements and audits to generate verified code updates.
Install
mkdir -p .claude/skills/specx && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18259" && unzip -o skill.zip -d .claude/skills/specx && rm skill.zipInstalls to .claude/skills/specx
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Spec-driven coding workflow for coderX agents. Use this skill whenever implementing, fixing, refactoring, or iterating code from hybrid docs or specified requirements, especially when file index, knowledge index, or evaluator findings are present.Key capabilities
- →Read specifications and acceptance criteria
- →Read engineering file index and knowledge index
- →Fix issues based on audit reports
- →Implement code changes based on execution brief
- →Verify code changes against acceptance criteria
- →Output verifiable code changes
How it works
This skill executes development by first reading specifications and acceptance criteria, then consulting engineering documents and knowledge graphs. It prioritizes audit feedback and implements changes verifiable against declared criteria.
Inputs & outputs
When to use specX
- →Implement feature spec
- →Refactor based on audit
- →Iterate from requirements
About this skill
specX
Read the dispatch action and referenced Task snapshot first, then its fixed acceptance/decision sources and relevant module boundaries. Expand only for named dependencies. Missing or contradictory execution grounds go to Main Agent; never guess scope.
Stay within Allowed Scope. Every Task is read-only to subagents: never change its metadata, body, timestamps, path or existence. Return required contract changes to Main Agent. Use engineeringX; return Change Summary + Note draft with actual checks and unresolved issues. Main Agent integrates them before the next handoff.
The prior conversation is optional. If the Task cannot support a fresh-session handoff, report the concrete missing reference or state.
When not to use it
- →When the Type 0 Dispatch Payload is missing Parent or Child paths
- →When the execution brief conflicts with current files or Child AC
- →When there is no active reference and no document record in context for non-xunit tasks
Limitations
- →Does not write to any document directly
- →Must not skip specification reading and directly code
- →Must not ignore the `Context Manifest`
How it compares
This skill enforces a spec-driven workflow by requiring explicit requirement alignment and context-oriented loading before implementation, ensuring changes are verifiable against acceptance criteria, unlike direct coding.
Compared to similar skills
specX side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| specX (this skill) | 0 | 3mo | No flags | Advanced |
| svelte-expert | 11 | 12mo | No flags | Intermediate |
| agent-implementer-sparc-coder | 1 | 8mo | Review | Intermediate |
| squirrel | 0 | 4mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
svelte-expert
Raudbjorn
Expert Svelte/SvelteKit development assistant for building components, utilities, and applications. Use when creating Svelte components, SvelteKit applications, implementing reactive patterns, handling state management, working with stores, transitions, animations, or any Svelte/SvelteKit development task. Includes comprehensive documentation access, code validation with svelte-autofixer, and playground link generation.
agent-implementer-sparc-coder
ruvnet
Agent skill for implementer-sparc-coder - invoke with $agent-implementer-sparc-coder
squirrel
Youssef-Ashraf2099
Full-cycle AI coding skill: plans, builds, tests, lints, fixes bugs, and writes production-grade docs. Auto-detects project state and adapts its 8-phase pipeline.
scaffold-feature
niklasbrandt
Scaffold a complete full-stack feature: FastAPI endpoint, dashboard Web Component, i18n keys, test stubs, and documentation checks.
coder
eq-lab
Implement a planned Pipeline GitHub Issue by number. Use when Codex is asked to execute an active plan end-to-end, update code/tests/docs, mark plan steps complete, run the relevant verification commands, and report results without editing issue labels, closing the Issue, moving the plan, or committ
bdd-feature-generator
rdkcentral
Generate BDD (Behavior Driven Development) feature files from tr69hostif source code analysis. Use for creating Gherkin-format documentation of TR-181 parameter handlers, daemon lifecycle, WebPA/Parodus communication, HTTP server protocol, and RFC store behavior. Produces gap analysis between featur