사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/wesleycamargo/devcontainer-template --skill sdlc-create-spec시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Create specification
Position
This stage follows an approved intent.md and creates sdlc/<work-item>/spec.md. It defines what the system must do; planning and production-code changes belong to later stages.
Inputs and output
- Required input: approved sdlc/<work-item>/intent.md.
- Also inspect relevant repository instructions, existing behavior, interfaces, dependencies, and architecture when needed to specify a compatible change.
- Output: a self-contained, scope-preserving spec.md in the same work item.
Responsibilities
Translate intent into clear observable functional requirements, relevant nonfunctional requirements, contracts, inputs, outputs, failure behavior, and testable acceptance criteria. Preserve existing public behavior when required. Use identifiers such as FR-1 only when they improve traceability. State security, compatibility, and operational requirements when applicable.
Repository inspection informs required behavior; it must not become a file-by-file implementation prescription. Prefer MUST, SHOULD, and MAY when they improve precision. Include positive, negative, and failure scenarios where relevant. Surface conflicts, missing requirements, and assumptions that could affect correctness.
Use only useful sections, typically:
`markdown
Specification: <Title>
Context
Goals
Non-Goals
Functional Requirements
Interfaces and Contracts
Error and Failure Behavior
Nonfunctional Requirements
Acceptance Criteria
Assumptions and Open Questions
If the intent cannot support a reliable specification, ask the question needed or return the intent for revision. Ask through the agent's interactive question tool (Claude Code: AskUserQuestion), grouping related questions in one call, with 2-4 suggested options each, the recommended one first and labeled "(Recommended)", so the user answers with buttons; use plain text only when no such tool exists. Do not generate tasks, prescribe implementation sequence, modify production code, expand scope, or create plan.md.
Handoff
After specification review and approval, hand off the work-item path to sdlc-create-plan. Changes to requirements or acceptance criteria require revising this artifact before replanning.
