Menu
Extracts structured requirements, acceptance criteria and risks from user requests and existing product documentation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Guides the creation and review of Architectural Decision Records (ADRs). Use this skill when a significant architectural change is proposed, a new technology is introduced, or a trade-off needs to be documented.
Intelligently routes requests to the correct context instructions and documentation files. Use this skill to determine which AGENT.md, guide, or technical instruction file is most relevant for a user's request.
Scaffold API mocking infrastructure using Mountebank and Testcontainers for reliable integration testing.
Manage full-stack observability using Logfire (logging/tracing) and OpenObserve (storage/visualization).
Interface for managing the Temporal Database and AI system (ReDB + GGUF embeddings).
Spec-Driven Development workflow using VibesPro conventions
| name | requirements-analysis |
| description | Extracts structured requirements, acceptance criteria and risks from user requests and existing product documentation. |
| metadata | {"id":"ce.skill.requirements-analysis","tags":["planning","product","context-min"],"inputs":{"files":["PRODUCT.md"],"concepts":["requirements"],"tools":["toolset:read"]},"outputs":{"artifacts":[],"files":[],"actions":["extract-requirements"]},"dependsOn":{"artifacts":["ce.doc.product"],"files":["PRODUCT.md"]},"related":{"artifacts":["ce.prompt.extract-requirements"],"files":[]}} |
This skill captures and structures user needs. Use it at the start of a new feature or when clarifying ambiguous requests.
Understand the request. Ask the user to describe the desired feature or change in their own words. Probe for the problem being solved, who benefits and any constraints or assumptions.
Review product context. Load PRODUCT.md and identify relevant goals, personas and
non‑goals. Use this context to anchor the requirements and avoid scope creep.
Elicit missing details. Pose concise questions to fill gaps in the problem description, such as expected input/output, performance targets, edge cases or regulatory constraints.
Define acceptance criteria. Translate the user’s needs into measurable acceptance criteria (e.g. “users can reset their password via email within 5 minutes”). Include edge cases and negative scenarios.
Identify risks and dependencies. Note any obvious risks (security, privacy, performance) and dependencies (other systems, APIs, skills). Capture these alongside the requirements.
Summarise and confirm. Present the structured requirements back to the user for confirmation. Adjust based on feedback until there is a shared understanding.
Capturing requirements thoroughly ensures subsequent planning, design and implementation phases are aligned with the user’s intent and product strategy.
