spec-creator

Create a Korean SPEC.md for new software projects through staged requirements discovery.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/byron1st/personal-harness --skill spec-creator-byron1st
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-creator
Source: https://github.com/byron1st/personal-harness/tree/main/skills/spec-creator
Command: npx skills add https://github.com/byron1st/personal-harness --skill spec-creator-byron1st

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a new project without a clear specification leads to vague plans and wrong assumptions downstream. This Skill guides you through a structured interview to produce a concrete, Korean-language SPEC.md that downstream planning and repo-setup skills can consume directly. ## Core Features & Use Cases - Four-stage discovery workflow: Seed, Deep Dive, Draft, and Refine stages walk you from a rough idea to a reviewed specification. - One-question-at-a-time interviewing: Targeted questions with trade-off options across tech stack, architecture, functional requirements, conventions, and constraints, skipping anything already answered. - Honest gap marking: Unknowns are flagged inline with [ASSUMED] markers or collected in an Open Questions section so planning tools surface them instead of baking in wrong assumptions. - Use Case: You have an idea for a Go REST API service. The Skill interviews you about runtime architecture, database, and business rules, then writes a complete Korean SPEC.md with ASCII architecture diagrams and implementable functional requirements. ## Quick Start Ask the assistant to help you create a SPEC.md for your new project idea and answer its questions one at a time.

Frequently Asked Questions about spec-creator

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

FAQPage Schema
How do I write a software specification document for a new project?▼

Describe your project idea, then answer targeted questions one at a time covering purpose, architecture, tech stack, functional requirements, and constraints. The Skill drafts a SPEC.md with a structured template and iterates with you section by section until you approve it.

What sections should a project SPEC.md include?▼

The template covers Tech Stack, Architecture (Context, Runtime, Code/Module), Conventions, Functional Requirements with inputs, outputs, and business rules, Quality Attributes, Constraints, Dependencies, and Open Questions for undecided items.

Can the specification be written in English instead of Korean?▼

No, the SPEC.md is always written in Korean regardless of conversation language, though technical terms like library names and CLI commands stay in English. The conversation itself follows your preferred language.

What happens when requirements are unclear or undecided?▼

Unclear items are marked inline with [ASSUMED] tags or listed in an Open Questions section rather than being invented. Downstream planning tools read these markers and ask about them at the right moment instead of baking wrong assumptions into a plan.

When should I not use a staged spec interview?▼

Skip it when a SPEC.md already exists and only needs edits, or when the project is trivial enough that a full specification adds no value. The Skill is designed for new projects starting from scratch, not incremental changes.