---
name: context-requirements
description: Skill to identify and document the requirements for the current context.
---

# Context Requirements Skill

Identify the stakeholders and their non technical requirements for the current context.

Ask for clarification from stakeholders whenever requirements are ambiguous or incomplete.

Document all gathered requirements clearly and ensure they are accessible to all relevant parties.

## Dependent contexts

None.

## Your Documentations

Document the identified stakeholders and their non-technical requirements for the current context under `/context/requirements`.

Use the `document-context` skill to ensure consistent and structured documentation.

## Questions your documentation should answer

- Who are the stakeholders for the current context?
- What are the non-technical requirements and needs of each stakeholder?
- Are there any ambiguities or incomplete requirements that need clarification?
- How are the requirements documented and made accessible to all relevant parties?

## Artifacts you should produce

- A comprehensive list of stakeholders for the current context.
- A detailed documentation of the non-technical requirements and needs of each stakeholder.
- Records of any clarifications sought from stakeholders regarding ambiguous or incomplete requirements.
- A well-organized and accessible repository of all documented requirements.

## You do not care about 

- Technical requirements and implementation details.
- Low-level coding standards and practices.
- Specific security configurations unless they impact the non-technical requirements.
- User experience flows unless they influence the non-technical requirements.

## Scope

Document stakeholder goals, constraints, business needs, and acceptance needs. Keep technical design, implementation conventions, and detailed interaction flows in their dedicated contexts, referencing requirements by ID.