/ 디렉터리 / 플레이그라운드 / spec-flow
● 커뮤니티 echoVic ⚡ 바로 사용

spec-flow

제작: echoVic · echoVic/spec-flow

Forces Claude Code through a 5-phase spec-driven workflow — Proposal, Requirements (EARS), Design, Tasks, Implementation — with living docs in .spec-flow/.

Spec-Flow is a skill that structures feature development as a gated pipeline. Each phase produces a Markdown artifact and pauses for your confirmation. Triggers include 'spec-flow', 'spec mode', 'need a plan', plus Chinese phrases '写个方案' and '做个规划'. Supports --fast (skip confirmations) and --skip-design flags.

왜 쓰나요

핵심 기능

라이브 데모

실제 사용 모습

spec-flow-skill.replay ▶ 준비됨
0/0

설치

작성자 저장소 · Claude Skills 공식 문서

사용 사례

실전 활용법: spec-flow

Turn a vague feature idea into a documented spec and implementation

👤 Engineers pushing back against 'just start coding' ⏱ ~60 min intermediate

언제 쓸까: PM handed you a one-liner and you'd rather spend 20 minutes writing a spec than 2 days writing the wrong code.

흐름
  1. Invoke the workflow
    spec-flow: add multi-region failover to our billing service.✓ 복사됨
    → Claude writes .spec-flow/proposal.md and waits for confirmation
  2. Confirm or edit each phase
    Proposal looks good — proceed to requirements.✓ 복사됨
    → requirements.md appears with EARS-format statements
  3. Implement from the task list
    Start the implementation phase. Work through tasks.md top-to-bottom.✓ 복사됨
    → Code changes that map 1:1 to task checkboxes

결과: A feature ships with the spec still alive in .spec-flow/ — future you can see why every decision happened.

함정
  • You're hacking a 10-minute fix and the skill adds 4 gates — Use --fast or just skip the skill for trivial work
함께 쓰기: github · filesystem

Reverse-engineer a spec for existing code before refactoring

👤 Engineers inheriting undocumented modules ⏱ ~45 min intermediate

언제 쓸까: About to refactor something nobody wrote a spec for.

흐름
  1. Ask Spec-Flow to backfill
    spec-flow --skip-design: backfill proposal and requirements.md for the existing src/auth module.✓ 복사됨
    → Clean EARS requirements extracted from actual code behavior
  2. Use the spec as refactor target
    Now design phase — how would we restructure while preserving these requirements?✓ 복사됨
    → design.md that maps new architecture to existing requirements

결과: A refactor grounded in a written contract instead of tribal knowledge.

함께 쓰기: filesystem

조합

다른 MCP와 조합해 10배 효율

spec-flow-skill + github

Commit .spec-flow/ artifacts alongside code so the spec lives in the repo history

After implementation, commit .spec-flow/ + src/ changes in one PR titled after the proposal.✓ 복사됨
spec-flow-skill + planning-with-files

Spec-Flow drives phase structure; planning-with-files keeps cross-session progress memory

Use spec-flow for the phases and planning-with-files for progress.md tracking across days.✓ 복사됨

도구

이 MCP가 노출하는 것

도구입력언제 호출비용
proposal_phase feature description Start of a new feature 0
requirements_phase approved proposal After proposal confirmed 0
design_phase approved requirements After requirements confirmed; skippable with --skip-design 0
tasks_phase approved design Before implementation 0
implementation_phase approved tasks Final phase — actually build it 0

비용 및 제한

운영 비용

API 쿼터
None
호출당 토큰
Each phase re-reads prior .spec-flow/ docs, so context grows across phases
금액
Free — skills are local files
팁
Use --fast on simple features; gates only earn their keep on 2+ day work.

보안

권한, 시크릿, 파급범위

자격 증명 저장: No credentials — pure prompts
데이터 외부 송신: None — .spec-flow/ stays in your working directory

문제 해결

자주 발생하는 오류와 해결

Wrong trigger keywords — Claude skips phases

Don't say '--fast' unintentionally. If you want full gates, omit flags and say 'spec-flow'.

대안

spec-flow 다른 것과 비교

대안언제 쓰나단점/장점
planning-with-filesYou want durable memory across sessions rather than phase gatingDifferent axis — complementary, not competing
Freeform devFeature is 1-2 hours of workFaster, but no audit trail

더 보기

리소스

📖 GitHub에서 공식 README 읽기

🐙 열린 이슈 보기

🔍 400+ MCP 서버 및 Skills 전체 보기