How do I install the Develop From Spec skill?

Run npx skillmds@latest add gabonio/develop-from-spec-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Develop From Spec safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Develop From Spec?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Develop From Spec free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Develop From Spec?

gabonio (@gabonio) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Develop From Spec by gabonio — Agent Skill

Name: Develop From Spec
Author: gabonio

Develop From Spec

Specification-driven workflow for non-trivial software changes. Use when the user explicitly invokes this skill, Builder Kit routes planned work here, or the user asks to discover, specify, plan, approve, implement, and verify a substantial feature. Enforce approval before implementation and use the plan as the executor handoff.

gabonio 27ce443 2 files · 2.7 KB Updated Sep 17, 2026

File contents

Develop from Spec

Workflow

Discover. Read local instructions, relevant architecture/design documents, neighboring code and tests, build/delivery rules, and sources of truth. Load only matching references and lenses.
Specify. Follow the repository's document convention. If none exists, propose docs/specs/YYYY-MM-DD-<feature>-design.md. Use the specification workflow and the template.
Approve the specification. For large or high-risk work, stop for this approval before writing the implementation plan.
Plan. Follow the repository convention or propose docs/plans/YYYY-MM-DD-<feature>-implementation.md. Use the plan template. Make it literal enough for a faster executor without duplicating the specification.
Approve the plan. Stop before implementation until the user unambiguously approves. Bounded features may receive combined specification-and-plan approval.
Execute. Follow ordered checkboxes, preserve unrelated work, make the smallest approved change, and record evidence. Ask for renewed approval on material drift.
Verify. Run focused checks while iterating and the closest local production-like build before PR readiness. Report exact evidence and unresolved risk.

Material drift

Stop for renewed approval before changing scope, acceptance criteria, architecture, public behavior, data/API contracts, dependencies, security or authorization boundaries, migrations, or deployment behavior. Small implementation details may change when they preserve the approved design; record meaningful deviations.

Executor handoff

The implementation plan is the handoff. Do not create a third summary. The executor follows concrete decisions, contracts, constraints, tests, stop conditions, and commands—not persona prompts or lens names. Recommend planning and execution capabilities using model profiles, not a permanently pinned model name.

---name: develop-from-spec-2description: Specification-driven workflow for non-trivial software changes. Use when the user explicitly invokes this skill, Builder Kit routes planned work here, or the user asks to discover, specify, plan, approve, implement, and verify a substantial feature. Enforce approval before implementation and use the plan as the executor handoff.---# Develop from Spec## Workflow1. **Discover.** Read local instructions, relevant architecture/design documents, neighboring code and tests, build/delivery rules, and sources of truth. Load only matching references and lenses.2. **Specify.** Follow the repository's document convention. If none exists, propose `docs/specs/YYYY-MM-DD-<feature>-design.md`. Use [the specification workflow](../../references/workflow/specification.md) and [the template](../../templates/specification.md).3. **Approve the specification.** For large or high-risk work, stop for this approval before writing the implementation plan.4. **Plan.** Follow the repository convention or propose `docs/plans/YYYY-MM-DD-<feature>-implementation.md`. Use [the plan template](../../templates/implementation-plan.md). Make it literal enough for a faster executor without duplicating the specification.5. **Approve the plan.** Stop before implementation until the user unambiguously approves. Bounded features may receive combined specification-and-plan approval.6. **Execute.** Follow ordered checkboxes, preserve unrelated work, make the smallest approved change, and record evidence. Ask for renewed approval on material drift.7. **Verify.** Run focused checks while iterating and the closest local production-like build before PR readiness. Report exact evidence and unresolved risk.## Material driftStop for renewed approval before changing scope, acceptance criteria, architecture, public behavior, data/API contracts, dependencies, security or authorization boundaries, migrations, or deployment behavior. Small implementation details may change when they preserve the approved design; record meaningful deviations.## Executor handoffThe implementation plan is the handoff. Do not create a third summary. The executor follows concrete decisions, contracts, constraints, tests, stop conditions, and commands—not persona prompts or lens names. Recommend planning and execution capabilities using [model profiles](../../references/model-profiles.md), not a permanently pinned model name.

Frequently asked questions