create-spec

Create implementation specs from codebase research with goals, design, and tests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn existing codebase research into a clear, implementation-ready specification for a feature, refactor, or system change.

Core Features & Use Cases

  • Research-Guided Planning: Uses findings from the research directory to ground the spec in real codebase context.
  • Boundary-Focused Design: Organizes the proposal around entrypoints, contracts, refusals, and irreversible effects.
  • Use Case: A team planning a new workflow or refactor can use this Skill to produce a structured RFC-style document that includes goals, architecture, risks, tests, and unresolved questions.

Quick Start

Ask the create-spec skill to draft a comprehensive implementation spec for the requested change using the relevant research in the codebase.

Frequently Asked Questions about create-spec

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

FAQPage Schema
How do I turn codebase research into an implementation spec for a new feature?ā–¼

To turn codebase research into an implementation spec, you map research notes and entrypoints to boundaries, then produce a structured RFC-style document covering goals, architecture, tests, and open questions.

What is the best way to write an RFC for a system refactor grounded in existing code?ā–¼

Writing an RFC for a system refactor involves organizing your proposal around entrypoints, contracts, refusals, and irreversible effects to ensure the design is fully grounded in real codebase context.

How do I plan a workflow change using entrypoint-driven design decisions?ā–¼

Planning a workflow change with entrypoint-driven design requires identifying valid skill-relevant research, mapping doors and boundaries, and defining the specific goals and tests for the proposed system change.

Do I need existing research notes before drafting a feature specification?ā–¼

Yes, you need existing research notes in your codebase's research directory before drafting a feature specification, as the Skill uses these findings to ground the design in actual codebase context rather than starting from scratch.

What should be included in an implementation spec for a codebase refactor?ā–¼

An implementation spec for a codebase refactor should include comprehensive goals, architecture design, boundary-focused contracts, testing plans, identified risks, and unresolved open questions based on your codebase research.