메뉴
Add a requirement (functional or non-functional)
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | blueprint:require |
| description | Add a requirement (functional or non-functional) |
| argument-hint | [requirement description] |
| allowed-tools | ["Glob","Grep","Read","Write","Edit","EnterPlanMode","ExitPlanMode"] |
COMMAND: Add a requirement to specs. Auto-detect type from description.
| Input contains | Type | File |
|---|---|---|
| "users can", "should be able to" | FR | docs/specs/features/[name].md |
| "P95", "latency", "under Xms" | NFR | docs/specs/non-functional/performance.md |
| "uptime", "availability" | NFR | docs/specs/non-functional/reliability.md |
| "encryption", "auth" | NFR | docs/specs/non-functional/security.md |
Source of truth: _templates/TEMPLATES.md
---
status: Active
maturity: Exploring
module: src/[module]/
related_adrs: []
---
# [Feature Name]
## Overview
[1-2 sentence description]
## User Stories
- As a [user type], I want [capability] so that [benefit]
## Requirements
- [Requirement 1]
## Implementation State
**Current focus:** TBD
**Open questions:**
- <!-- TODO: Add open questions -->
## Acceptance Criteria
<!-- TODO: Add when ready for test automation -->
---
category: Performance | Security | Scalability | Reliability
---
# [Category] Requirements
| Metric | Target | Measured At |
|--------|--------|-------------|
| [metric] | [target] | [location] |
## [Specific Requirement]
**Requirement:** [Measurable statement]
**Rationale:** [Why this matters]
Added requirement to docs/specs/[path]
If details missing, use TBD markers.
Capture decisions and context from the current conversation into blueprint docs, DESIGN.md, and design trees
Record a decision or cross-cutting design rule with rationale. Triages tech vs UX vs DESIGN.md rules vs requirements into the right document type and tree.
Explain Blueprint Mode plugin and available commands. Use when the user asks about Blueprint features, how to use skills, or needs guidance on the intent-capture workflow.
Opt-in. Add design intent capture to a Blueprint repo. Scaffolds design/ux-decisions/, offers to scaffold a minimal community-format DESIGN.md if absent, and can optionally surface a small number of candidate UX decisions found in existing UI/code for the user, developer, or designer to confirm.
Create Blueprint structure from existing repo. Run multiple times to refine.
Show overview of project's Blueprint structure plus important adjacent DESIGN.md context. Use when the user asks about documented decisions, project status, or wants to see what's been captured.