skills.rest
rootspec
rootspecOFFICIAL
Explore all skills by this author →
GitHub

rs-impl

Convert validated RootSpec stories into code scaffolds and test suites.

Updated Nov 7, 2025
Search Tags:#automation#workflow#testing#tdd#implementation#spec#ai-agent
One-click install
npx skills add https://github.com/rootspec/rootspec --skill rs-impl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rs-impl
Source: https://github.com/rootspec/rootspec/tree/main/skills/rs-impl
Command: npx skills add https://github.com/rootspec/rootspec --skill rs-impl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates validated RootSpec stories into working code and tests, reducing manual guesswork and speeding up delivery.

Core Features & Use Cases

  • Spec-to-implementation automation: Converts validated stories into code scaffolds and test suites with minimal human input.
  • Non-interactive execution: Runs without prompts, surfacing uncertainties for later review.
  • Progress tracking & reporting: Records iteration timestamps and per-story attempts, exporting status on completion.

Quick Start

Provide a validated RootSpec and start rs-impl to begin implementing features from the spec in a non-interactive, autonomous workflow.

Frequently Asked Questions about rs-impl

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

FAQPage Schema
How do I automate feature implementation from a validated spec?▼

Spec-driven feature implementation is automated by converting validated user stories into ready-to-run code and test suites. This Skill autonomously generates the scaffolding and tests with minimal human input, speeding up delivery.

Can I run spec-to-implementation automation without interactive prompts?▼

Yes, non-interactive execution runs the implementation workflow without prompts. It processes validated stories autonomously and surfaces any uncertainties encountered during code generation for later review.

How does test-driven implementation work when generating code from a spec?▼

Test-driven implementation enforces creating and validating tests alongside code generation. The workflow converts stories into test suites first, ensuring the autonomously generated code scaffolds meet the spec requirements.

Do I need a validated RootSpec before starting automated implementation?▼

Yes, a validated RootSpec is required. You must provide validated user stories beforehand so the automation can accurately translate them into working code scaffolds and corresponding test suites.

Does autonomous spec implementation track progress and iteration attempts?▼

Progress tracking records iteration timestamps and per-story attempts during implementation. It exports the completion status and metadata, ensuring you have a full report of the automated workflow's execution.

What is the best way to fix failing tests in an automated spec workflow?▼

Automated test fixing is handled by running the implementation workflow against the failing tests. It autonomously iterates through the spec stories to correct the code and records the attempt metadata until the tests pass.

Related Skills

Explore More Software Engineering Skills→
dceoydceoy
120

speckit-baseline

Analyze source code to generate feature specifications with user stories and acceptance criteria.

Community
Advanced
WizarckWizarck

bmad-review-edge-case-hunter

Enumerate branching paths and report unhandled edge cases in code, diffs, or specs.

Community
Advanced
hffmnnjhffmnnj
39

testing

Automate unit, integration, and E2E tests in JavaScript/TypeScript projects.

Community
Intermediate
lofidonut3lofidonut3
2

speckit.clarify

Ask up to 5 targeted clarification questions and encode answers into a feature spec.

Community
Basic