implement-from-spec

Convert requirements documents into executable implementations with subagent orchestration.

Updated Mar 25, 2026

Search Tags:#workflow #planning #specification #implementation #subagents #orchestration #traceability

Ready to run

npx skills add https://github.com/yamk12nfu/claude-skills --skill implement-from-spec-yamk12nfu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement-from-spec
Source: https://github.com/yamk12nfu/claude-skills/tree/main/implement-from-spec
Command: npx skills add https://github.com/yamk12nfu/claude-skills --skill implement-from-spec-yamk12nfu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts requirements documents into executable implementations.

Core Features & Use Cases

Orchestrates end-to-end spec-to-implementation by validating the spec, extracting tasks, creating a plan, and delegating work to subagents with clear traceability.
Maintains global constraints, progress logs, and implements a strict review loop to ensure spec compliance and code quality.
Suitable for teams that want a repeatable, auditable workflow from requirements to delivery.

Quick Start

Provide the path to the requirements document to start the end-to-end spec-to-implementation orchestration.

Frequently Asked Questions about implement-from-spec

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

FAQPage Schema

How do I convert a requirements document into executable code automatically?▼

To convert a requirements document into executable code, you provide the spec path to trigger end-to-end orchestration. The workflow validates the specification, extracts tasks, creates a plan, and delegates implementation to subagents.

How does subagent-driven task decomposition work for specification implementation?▼

Subagent-driven task decomposition works by extracting tasks from a validated spec and delegating each task to subagents. This orchestrated execution maintains strict traceability and enforces global constraints across all generated code.

What is the best way to maintain traceability from requirements to code delivery?▼

The best way to maintain traceability from requirements to delivery is using an orchestrated workflow that logs progress and implements strict review loops. This ensures spec compliance and code quality across all delegated subagent tasks.

Can I enforce coding conventions and non-functional requirements during automated implementation?▼

You can enforce coding conventions and non-functional requirements during automated implementation through phased reviews. The orchestration process applies these global constraints across all subagent-executed tasks to ensure compliance.

Does spec-to-implementation orchestration work without external dependencies?▼

Spec-to-implementation orchestration works without external dependencies. It uses an internal subagent architecture to decompose plans, execute tasks, and maintain progress records independently.

When should I use an orchestrated workflow for software implementation?▼

You should use an orchestrated workflow for software implementation when you need a repeatable, auditable pipeline from requirements to delivery. It is ideal for teams requiring strict spec compliance and phased review loops.