skills.rest
Ferreira-Jefferson
Ferreira-JeffersonCOMMUNITY
Explore all skills by this author →
GitHub

spec-creator

Generate a phase-driven specification package before code implementation.

1|Updated Apr 17, 2026
Search Tags:#automation#workflow#documentation#spec#phases#sdD
One-click install
npx skills add https://github.com/Ferreira-Jefferson/j-skills --skill spec-creator-ferreira-jefferson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-creator
Source: https://github.com/Ferreira-Jefferson/j-skills/tree/main/spec-creator
Command: npx skills add https://github.com/Ferreira-Jefferson/j-skills --skill spec-creator-ferreira-jefferson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec-Driven Development (SDD) ensures teams generate a complete, verifiable spec package before implementation, reducing rework and scope creep.

Core Features & Use Cases

  • Structured, phase-driven workflows: Discovery, SPEC, REQUIREMENTS, DESIGN, TEST-PLAN, TASKS, REVIEW-FINAL, START.
  • Automated governance: Gatekeeping with a senior spec-reviewer to ensure consistency and completeness.
  • Documentation-first handoff: Outputs a complete spec package that a separate implementation session can execute from START.

Quick Start

Instruct the agent to trigger spec-creation for a feature you want to develop and follow the phase-by-phase prompts to generate a complete spec package.

Frequently Asked Questions about spec-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is spec-driven development and how does it prevent scope creep?▼

Spec-driven development generates a complete, verifiable specification package before implementation begins, ensuring teams define features thoroughly to reduce rework and scope creep.

How do I generate a complete software specification package before writing code?▼

Trigger spec-creation for your feature and follow phase-by-phase prompts through Discovery, SPEC, REQUIREMENTS, DESIGN, TEST-PLAN, TASKS, REVIEW-FINAL, and START to generate the package.

Can I use an automated workflow to enforce gated reviews during software documentation?▼

Yes, the workflow applies automated governance using a senior spec-reviewer to gatekeep phases, ensuring consistency and completeness before allowing explicit handoffs between them.

What's the best way to structure feature discovery and requirements documentation?▼

Structure feature discovery using a phase-driven workflow that moves sequentially from Discovery to REQUIREMENTS, producing documentation-first handoffs that ensure traceability and quality.

Does spec-driven development require any specific frameworks or dependencies to run?▼

No, spec-driven development operates with no external dependencies, requiring only an agent instructed to trigger spec-creation and follow the structured phase prompts.

When should I not use a phase-driven specification workflow for my project?▼

Avoid phase-driven specification workflows if your project requires immediate code output without upfront documentation, as this process enforces structured discovery and gated reviews before implementation.

Related Skills

Explore More Software Engineering Skills→
DuongMQuangDuongMQuang
6

0-init

Automate project setup by generating CONTEXT.md and OPEN_QUESTIONS.md.

Community
Intermediate
dfrysingerdfrysinger
36

test

Run acceptance tests against implemented code and present pass/fail results.

Community
Advanced
thanh-abaiithanh-abaii
34

gs:land-and-deploy

Merge pull requests, run CI/CD pipelines, and verify production health.

Community
Advanced
AbsolutelySkilledAbsolutelySkilled
207

user-stories

Generate user stories and acceptance criteria using INVEST and Given/When/Then templates.

Official
Advanced