Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

spec-driven-development

Estrellas12

Forks2

Actualizado12 de mayo de 2026 a las 06:28

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

WodenWang820118

WodenWang820118/tag-check

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

Explorador de archivos

3 archivos

SKILL.md

readonly

name	spec-driven-development
description	Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.

Spec-Driven Development

Planning skill for new features and significant changes. Its job is to produce a reviewable spec before implementation starts.

When to Use

New features or significant behavior changes.
Requirements are ambiguous or the task needs architectural decisions.
Public contracts, data flow, or boundaries need to be made explicit.

Do not use for typo fixes, clearly mechanical changes, or already-specified one-file edits.

Load / Do Not Load

Load this skill during planning after using-agent-skills selects it.
Keep planning-and-task-breakdown, incremental-implementation, test-driven-development, and code-review-and-quality unloaded until this spec is ready for handoff.

Core Workflow

Confirm the Framing: If the request still feels solution-framed or the real product goal is unclear, route through product-and-scope-review first and record the chosen scope mode.
Surface Assumptions: State what you are assuming about the request, especially anything that would change scope, architecture, contracts, or dependencies.
Define Success Criteria: Reframe vague requests into concrete, testable outcomes before drafting the spec.
Draft the Spec: Cover objective, tech stack, commands, project structure, code style example, testing strategy, boundaries or non-goals, success criteria, and open questions.
Save the Spec: For non-trivial work, save the spec to a repo file so it can be reviewed and updated.
Plan Review Checkpoint: Route the spec through the mandatory Plan Review before moving to task breakdown or implementation.
Keep It Current: Update the spec first if scope, contracts, data model, or architecture decisions change during the task.

Ask / Escalate

Ask when success criteria, boundaries, or non-goals remain ambiguous after bounded discovery.
Stop and escalate rather than guessing about public contracts, data model changes, auth or security boundaries, CI changes, or new dependencies.

References

Detailed guidance: references/guidance.md
Spec template: references/spec-template.md

Más de este repositorio

mismo repositorio

agent-preflight

WodenWang820118/tag-check

Pre-flight checklist that every primary agent runs before opening the pre-implementation gate. Confirms task size, primary AI family, cross-family reviewer routing, grill-me requirement, and the exact `pnpm review:approve-pre-implementation` flags to use.

2026-05-2612

using-agent-skills

WodenWang820118/tag-check

Discovers and invokes the repo-local skill set. Use when starting work or when you need to choose the right workflow for the current task.

2026-05-2612

angular-patterns

WodenWang820118/tag-check

Repo-specific Angular conventions and patterns for law-prep-web. Load when working with Angular components, services, DI, signals, routing, or tests.

2026-05-1212

grill-me

WodenWang820118/tag-check

Repo-local overlay of the cross-family grill-me skill. Stress-test a plan or design through one-question-at-a-time interviews, with a 6-item completion checklist required before Plan Review for medium+ or sensitive tasks.

2026-05-1212

incremental-implementation

WodenWang820118/tag-check

Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.

2026-05-1212

nx-import

WodenWang820118/tag-check

Import, merge, or combine repositories into an Nx workspace using nx import. USE WHEN the user asks to adopt Nx across repos, move projects into a monorepo, or bring code/history from another repository.

2026-05-1212

Spec-Driven Development

Planning skill for new features and significant changes. Its job is to produce a reviewable spec before implementation starts.

When to Use

New features or significant behavior changes.

Requirements are ambiguous or the task needs architectural decisions.

Public contracts, data flow, or boundaries need to be made explicit.

Do not use for typo fixes, clearly mechanical changes, or already-specified one-file edits.

Load / Do Not Load

Load this skill during planning after using-agent-skills selects it.

Keep planning-and-task-breakdown, incremental-implementation, test-driven-development, and code-review-and-quality unloaded until this spec is ready for handoff.

Core Workflow

Confirm the Framing: If the request still feels solution-framed or the real product goal is unclear, route through product-and-scope-review first and record the chosen scope mode.

Surface Assumptions: State what you are assuming about the request, especially anything that would change scope, architecture, contracts, or dependencies.

Define Success Criteria: Reframe vague requests into concrete, testable outcomes before drafting the spec.

Draft the Spec: Cover objective, tech stack, commands, project structure, code style example, testing strategy, boundaries or non-goals, success criteria, and open questions.

Save the Spec: For non-trivial work, save the spec to a repo file so it can be reviewed and updated.

Plan Review Checkpoint: Route the spec through the mandatory Plan Review before moving to task breakdown or implementation.

Keep It Current: Update the spec first if scope, contracts, data model, or architecture decisions change during the task.

Ask / Escalate

Ask when success criteria, boundaries, or non-goals remain ambiguous after bounded discovery.

Stop and escalate rather than guessing about public contracts, data model changes, auth or security boundaries, CI changes, or new dependencies.

References

Detailed guidance: references/guidance.md

Spec template: references/spec-template.md