skills.rest
i-standard1
i-standard1OFFICIAL
Explore all skills by this author →
GitHub

spec-feature

Reverse-engineer implemented code into formal requirements definitions mapped in spec-map.yml.

6|2|Updated Apr 5, 2026
Search Tags:#automation#documentation#requirements#traceability#code-analysis#spec-writing#reverse-engineering
One-click install
npx skills add https://github.com/i-standard1/yamasaki --skill spec-feature-i-standard1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-feature
Source: https://github.com/i-standard1/yamasaki/tree/main/.claude/skills/spec-feature
Command: npx skills add https://github.com/i-standard1/yamasaki --skill spec-feature-i-standard1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Existing codebases often lack formal requirements. This skill analyzes implemented code to automatically generate requirements definitions (what) and records the mapping between code and specs in spec-map.yml (no code changes). It is used when you want to convert an existing feature or functionality into a formal spec, such as turning "tweet" or "authentication" into documented requirements, or when you need to align current specs with live code.

Core Features & Use Cases

  • Reverse-engineer specs from implemented code and generate requirements definitions.
  • Maintain code-to-spec mappings in spec-map.yml to ensure traceability.
  • Update or draft specs for existing features by referencing shared spec-writing standards.

Quick Start

Transform the current code for a chosen feature into a requirements definition using spec-feature.

Frequently Asked Questions about spec-feature

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

FAQPage Schema
How do I generate requirements documentation from existing source code?▼

To generate requirements documentation from existing source code, reverse-engineer the implemented functionality to automatically extract formal requirements definitions and map them in spec-map.yml for traceability.

What is the best way to maintain traceability between code and formal specs?▼

Maintaining traceability between code and formal specs requires mapping implemented functionality to requirements definitions in spec-map.yml, ensuring each requirement has a clear origin in the source code and documented relationships to existing specs.

How do I reverse-engineer a mature codebase into a specification?▼

Reverse-engineering a mature codebase into a specification involves analyzing implemented code to extract functionality and drafting formal requirements definitions that align with shared spec-writing standards without altering the original source.

Can I align my current requirements with live code without modifying the codebase?▼

Yes, you can align current requirements with live code without modifying the codebase by analyzing existing functionality and updating the requirements definitions and code-to-spec mappings in spec-map.yml to reflect the actual implementation.

When do I need to reverse-engineer specs from implemented features?▼

You need to reverse-engineer specs from implemented features when an existing codebase lacks formal requirements documentation and you must generate, update, or synchronize requirements definitions for mature feature groups.

Does generating requirements definitions from code work for mature codebases and feature groups?▼

Generating requirements definitions from code is specifically applicable to mature codebases and feature groups where you need to map implemented functionality to formal specs and maintain ongoing documentation synchronization.

Related Skills

Explore More Software Engineering Skills→
EmpoweredHouseEmpoweredHouse

speckit-baseline

Analyze source files to extract structure and behavior for spec generation.

Official
Intermediate
i-standard1i-standard1
6

update-docs

Propagate git-tracked code changes into design docs and OpenAPI specs.

Official
Advanced
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate
re-cinqre-cinq
20

spec-driven-development

Convert formal specifications into executable tests and living documentation.

Official
Advanced