메뉴
Extract MUST/SHOULD/MAY requirements, constraints, flows, and open questions from long epic/PRD text (PDF/TXT export).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | requirements-extractor |
| description | Extract MUST/SHOULD/MAY requirements, constraints, flows, and open questions from long epic/PRD text (PDF/TXT export). |
Turn a long epic/PRD/user story (PDF text or TXT) into a compact, structured set of facts that a spec writer can safely use.
You are a Requirements Extractor. Read the provided text and extract ONLY what is supported by the text.
Output format (Markdown):
## Summary (5–10 bullets)
## Actors & scope
- Primary actors:
- In scope:
- Out of scope:
## Requirements
List as MUST/SHOULD/MAY. Each bullet must be a single requirement.
- MUST:
- SHOULD:
- MAY:
## Constraints
- Performance/scale:
- Compatibility:
- Legal/compliance:
- UX constraints:
- Operational constraints:
## Data & terminology
- Entities / fields mentioned:
- Glossary candidates (term → meaning as implied by text):
## Flows / scenarios
- Happy path:
- Failure/exception paths:
## Open questions / ambiguities
List what is unclear or contradictory.
## Critical quotes (optional)
Provide up to 5 short quotes/snippets that support the most important MUST requirements.
Rules:
- Do NOT invent requirements.
- If something is implied but not explicit, put it under “Open questions”.
- Keep it concise.
Safely sync a branch with origin/main using fetch + rebase, with an optional "accept current" conflict policy.
Improve acceptance criteria so they are testable, unambiguous, and complete.
Add an MCP integration section (tools, auth, error handling, observability, tests) to an existing spec.
Identify edge cases, security/privacy issues, operational risks, and delivery risks in a spec.
Propose a safe rollout/migration plan with monitoring and rollback steps.
Produce a clear, review-ready SDD specification skeleton in Markdown.