spec-to-impl

Transform feature specifications into sequenced implementation prompts.

29|6|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/edictum-ai/edictum --skill spec-to-impl-edictum-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-to-impl
Source: https://github.com/edictum-ai/edictum/tree/main/.claude/skills/spec-to-impl
Command: npx skills add https://github.com/edictum-ai/edictum --skill spec-to-impl-edictum-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The Skill unit "spec-to-impl" solves the problem of transforming feature specifications into detailed, audited implementation prompts, streamlining the process from design to code for software development projects.

Core Features & Use Cases

  • Spec Audit: Evaluates feature specs against project rules for consistency and adherence to guidelines.
  • Gap Identification: Identifies missing information or discrepancies in the spec that need to be addressed.
  • Decision Collection: Collects decisions on identified issues for implementation guidance.
  • Prompt Generation: Generates sequenced prompts that guide the implementation process step-by-step.

Quick Start

Run the 'spec-to-impl' skill with a feature spec file to generate implementation prompts.

Frequently Asked Questions about spec-to-impl

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

FAQPage Schema
How do I convert feature specifications into implementation prompts?

To convert feature specifications into implementation prompts, you can use a spec-to-impl process that evaluates your spec against project rules, identifies gaps, collects decisions, and generates sequenced prompts for step-by-step code generation.

What is the best way to audit feature specs for code generation?

Auditing feature specs for code generation involves evaluating the specification against established project rules to identify missing information, collect necessary decisions, and ensure consistency before generating implementation prompts.

How do I identify gaps in a software specification before implementation?

You identify gaps in a software specification by evaluating the feature spec against project rules to detect missing information and discrepancies, then collecting decisions on those issues to guide the implementation process.

Can I generate sequenced prompts for software development from a feature spec?

Yes, you can generate sequenced prompts for software development by processing a feature spec file through a specification audit, resolving identified gaps, and outputting step-by-step implementation guidance.

Does spec-to-impl work with existing project rules and guidelines?

Yes, the spec-to-impl process evaluates your feature specifications directly against existing project rules and guidelines to check for consistency and adherence before generating the implementation prompts.

What are the limitations of generating implementation prompts from specs?

Generating implementation prompts from specs relies on the completeness of the initial feature specification; if gaps are identified, you must collect decisions on those missing issues before the sequenced prompts can be fully generated.