메뉴
OpenSpec spec-driven development workflow for creating proposals, writing delta specs, and archiving changes. Use when working with the openspec/ directory or managing the proposal-to-archive lifecycle.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
Fetching and addressing GitHub PR review comments from Copilot, Greptile, and human reviewers. Includes provider-calibrated triage, verification, ticket management, and conditional spec updates. Use when in review mode or when PR feedback needs to be addressed.
Fetching and addressing GitHub PR review comments from Copilot, Greptile, and human reviewers. Includes provider-calibrated triage, verification, ticket management, and conditional spec updates. Use when in review mode or when PR feedback needs to be addressed.
Core Ralph Loop workflow orchestration. Use when running autonomous development iterations, selecting modes, or making decisions about the build/interview/bootstrap/archive lifecycle.
Core Ralph Loop workflow orchestration. Use when running autonomous development iterations, selecting modes, or making decisions about the build/interview/bootstrap/archive lifecycle.
How to run and interpret backpressure checks. Use before committing code to ensure quality gates pass.
| <!-- sync | openspec --> |
| name | openspec-workflow |
| description | OpenSpec spec-driven development workflow for creating proposals, writing delta specs, and archiving changes. Use when working with the openspec/ directory or managing the proposal-to-archive lifecycle. |
OpenSpec maintains living system documentation through a proposal -> implement -> archive lifecycle.
openspec/
├── specs/ # Source of truth: how the system works NOW
│ └── <domain>/
│ └── spec.md
├── changes/ # Active proposals (one folder per change)
│ └── <change-id>/
│ ├── .openspec.yaml # Schema and metadata
│ ├── README.md # Change description
│ ├── proposal.md # Why: intent, scope, capabilities (artifact 1)
│ ├── design.md # How: technical approach (artifact 2)
│ ├── specs/ # What: delta specs (artifact 3)
│ │ └── <domain>/
│ │ └── spec.md
│ └── tasks.md # Task breakdown (artifact 4)
└── config.yaml # Optional configuration
Artifacts have a dependency chain: proposal → design + specs → tasks.
Use npx openspec status --change <id> to see which artifacts are complete.
npx openspec new change <change-id> # Create change folder
npx openspec status --change <change-id> # Check artifact completion
npx openspec instructions <artifact> --change <id> # Get artifact template
npx openspec show <change-id> # View change proposal
npx openspec list # List active changes
npx openspec validate <change-id> # Validate spec format
npx openspec archive <change-id> -y # Merge deltas into specs/
Delta specs describe what's changing relative to current specs:
# Delta for <Domain>
## ADDED Requirements
### Requirement: Feature Name
The system SHALL [behavior description].
#### Scenario: Happy path
- GIVEN [precondition]
- WHEN [action]
- THEN [expected result]
## MODIFIED Requirements
### Requirement: Existing Feature
The system SHALL [updated behavior].
(Previously: [old behavior])
## REMOVED Requirements
### Requirement: Deprecated Feature
(Reason for removal)
When npx openspec archive <change-id> -y runs:
openspec/changes/archive/<date>-<change-id>/