create-spec

Generate technical design documents from existing research directories.

484|76|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/flora131/atomic --skill create-spec-flora131
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-spec
Source: https://github.com/flora131/atomic/tree/main/.opencode/skills/create-spec
Command: npx skills add https://github.com/flora131/atomic --skill create-spec-flora131

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of creating comprehensive technical specifications for features or refactors by leveraging existing research within a codebase.

Core Features & Use Cases

  • Automated Spec Generation: Creates detailed technical design documents (RFCs) based on provided research.
  • Research Integration: Utilizes findings from specified research directories to inform the spec.
  • Use Case: After researching a new authentication flow, use this Skill to generate a full technical spec, including architecture diagrams, API definitions, and data models, ready for review.

Quick Start

Use the create-spec skill to generate a technical specification for the research found in the 'research/authentication' directory.

Frequently Asked Questions about create-spec

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

FAQPage Schema
How do I generate a technical specification from existing codebase research?

Generate technical specifications from existing research by analyzing documents in a specified research path to produce a structured RFC with executive summary, context, goals, design, and open questions sections.

What is the best way to create an RFC for a feature refactor using prior research?

Creating an RFC for a refactor is best handled by leveraging existing codebase research findings to automatically generate a detailed technical design document, integrating architecture definitions and prompting for clarification on unresolved issues.

Does this spec generation approach work with research from any directory path?

Spec generation works with any specified research directory path, utilizing codebase research agents to analyze the contained documents and inform the resulting technical specification.

How do I ensure open questions in my technical design document are resolved?

Resolve open questions in a technical design document through the Skill's interactive clarification mechanism, which prompts the user directly for input on unresolved issues identified during research analysis.

What sections are included in an automated technical specification?

An automated technical specification includes structured sections for an executive summary, context, goals, design, and open questions, providing a comprehensive RFC ready for review.

When should I not use automated RFC generation for planning?

Avoid automated RFC generation when no prior codebase research documents exist, as the specification process relies entirely on analyzing existing research findings within a specified directory to inform the output.