skills.rest
coakenfold
coakenfoldCOMMUNITY
Explore all skills by this author →
GitHub

spec

Generate implementation-ready Markdown specifications from feature ideas.

Updated Feb 11, 2026
Search Tags:#planning#documentation#specification#requirements#design-doc#feature-idea
One-click install
npx skills add https://github.com/coakenfold/p-100226 --skill spec-coakenfold
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/coakenfold/p-100226/tree/main/.claude/skills/spec
Command: npx skills add https://github.com/coakenfold/p-100226 --skill spec-coakenfold

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform vague feature ideas into concrete, implementation-ready specifications to align planning and coding across teams.

Core Features & Use Cases

  • Generates a formal spec document with sections such as Problem Statement, Approach, Implementation Requirements, API Contracts, and Data Model changes.
  • Parses a feature idea or description, researches the codebase to identify conventions, patterns, and impacted layers (frontend, backend, shared types, tests).
  • Writes the spec to docs/specs/<feature-name>.spec.md for traceability and handoff to implementation.

Quick Start

Provide a feature name or description as input and run the Spec Generator to create docs/specs/<feature-name>.spec.md.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I generate an implementation-ready specification from a feature idea?▼

To generate an implementation-ready specification, provide a feature idea or description as input. The tool parses the input, researches existing codebase patterns, and outputs a structured Markdown spec document to docs/specs.

What sections should a design doc include for backend and frontend planning?▼

A design doc specification should include a Problem Statement, Approach, Implementation Requirements, API Contracts, and Data Model changes. These sections align planning and coding across teams by detailing impacted frontend, backend, and shared type layers.

How do I write a spec that identifies affected components and artifacts?▼

Writing a spec that identifies affected components requires parsing a feature description and researching the codebase. The process detects existing conventions and automatically maps impacted layers like shared types and tests into a Markdown spec.

Can I use this specification generator for frontend, backend, and shared types?▼

Yes, you can use this specification generator for frontend, backend, and shared types. It researches your codebase to identify conventions and patterns across all layers, ensuring the formal spec accurately bridges ideation and coding.

What is the best way to turn vague feature ideas into concrete requirements?▼

The best way to turn vague feature ideas into concrete requirements is to parse the description and research codebase patterns. This generates a formal specification with defined API Contracts and Data Model changes for team handoff.

Where does the generated feature specification document get saved?▼

The generated feature specification document gets saved directly to docs/specs/<feature-name>.spec.md. This Markdown output ensures traceability and provides a structured handoff artifact for implementation.

Related Skills

Explore More Software Engineering Skills→
ThuHuynh1438ThuHuynh1438

block

Track project blockers with severity, owner, and due date.

Community
Intermediate
ChoiHyunjinChoiHyunjin

role-backend-developer

Implement RESTful APIs, business logic, and data access layers from specifications.

Community
Advanced
Intense-VisionsIntense-Visions
18

harness-api-design

Generate versioned OpenAPI, GraphQL, or proto specifications from existing API surfaces.

Official
Advanced
vecearvecear

rfc-generator

Generate RFC documents with standardized sections for proposals and reviews.

Community
Advanced