refine-spec

Refine draft feature specifications into structured implementation-ready documents.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/reckerswartz/resume_builder --skill refine-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refine-spec
Source: https://github.com/reckerswartz/resume_builder/tree/main/.devin/skills/refine-spec
Command: npx skills add https://github.com/reckerswartz/resume_builder --skill refine-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

refine-spec helps teams convert a rough draft feature specification into a precise, implementation-ready design by guiding targeted clarifying questions across key domains.

Core Features & Use Cases

  • Guided Q&A across scope, users, data, integration, and non-functional requirements to surface ambiguities.
  • Structured summary generation that can be dropped into a project specs folder as a [feature-name]-specification.md.
  • Optional artifacts generation (e.g., TDD/implementation plan) to accelerate planning and alignment.

Quick Start

Submit your draft specification to begin the guided refinement session.

Frequently Asked Questions about refine-spec

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

FAQPage Schema
How do I refine a draft feature specification into an implementation-ready document?

To refine a draft feature specification, you submit the draft to a guided Q&A process that surfaces ambiguities across scope, data models, and integrations, producing a structured final spec saved as [feature-name]-specification.md.

What questions should I ask when clarifying requirements for a Rails web product spec?

Clarifying requirements for a Rails web product spec involves asking targeted questions across scope, users, data, integrations, and non-functional requirements to resolve ambiguities before implementation begins.

How do I structure a feature specification to cover data models and non-functional requirements?

Structuring a feature specification requires guided refinement across key domains like data models and non-functional requirements, resulting in a structured summary document that can be dropped directly into your project specs folder.

Can I use this specification refinement process for any web product or just Rails?

The specification refinement process applies to Rails and web product specs, guiding targeted clarifying questions across scope, data, integrations, and non-functional requirements to produce implementation-ready documents.

What is the best way to turn a rough draft spec into an implementation plan?

The best way to turn a rough draft spec into an implementation plan is through guided clarification that generates a structured specification summary, optionally producing artifacts like TDD plans to accelerate alignment.