explore-requirements

name	explore-requirements
description	Define the functional and non-functional business requirements, mapping user needs to technical capabilities. Codex repo skill for the legacy /tangram:explore-requirements workflow.

Codex adaptation: this skill was promoted from .codex/workflows/tangram/skills/explore-requirements. Use it explicitly as $explore-requirements, or ask for the matching Tangram workflow in natural language. Internal Tangram knowledge has been mirrored to .agents/knowledge.

You are the Tangram Build AI executing the explore-requirements skill. Your goal is to transform user needs and PRD snippets into a structured list of requirements within tangram/studies/business-requirements.md.

Input: Triggered by /tangram:explore-requirements. This is the primary entry point for PRD data. The user should provide a list of features or a full PRD (e.g., /tangram:explore-requirements [paste PRD here]).

Steps

1. Read Context Read tangram/overview.md and tangram/studies/goal.md. Requirements must directly serve the North Star goal established in the previous phase.

2. Deconstruct the PRD Analyze the user input to separate:

   • Functional Requirements: What the system does (e.g., "User can login").
   • Non-Functional Requirements: How the system behaves (e.g., "Page must load in under 2 seconds").
   • Constraints: External factors (e.g., "Must comply with GDPR").

3. Clarify Ambiguities If a requirement is vague (e.g., "Make it fast"), ask for a metric. Example: "You mentioned 'Fast performance'—should we aim for a specific sub-second load time or a maximum number of concurrent users?"

4. Suggest the Draft Generate a draft for tangram/studies/business-requirements.md using the template below. Do not write the file yet. Just show the suggested content.

5. Wait for Approval Ask: "Does this capture the full scope of the business requirements, or are we missing any critical edge cases?" Pause and wait for the user's response.

6. Summarize and Write Once approved, write the finalized content to tangram/studies/business-requirements.md. Announce that the business requirements are locked.

7. Confirm Next Step Inform the user: "Scope defined! We can now move to /tangram:explore-legacy to check for technical compatibility, or /tangram:explore-monetization to define the revenue model."

---

Draft Template for tangram/studies/business-requirements.md

# Business Requirements Document (BRD)

## 1. User Personas & Roles

- **[Persona A]:** [e.g., Admin] - Needs to [Main Goal].
- **[Persona B]:** [e.g., End User] - Needs to [Main Goal].

## 2. Functional Requirements (FR)

| ID    | Requirement    | Priority   | Description                     |
| ----- | -------------- | ---------- | ------------------------------- |
| FR-01 | [Feature Name] | [P0/P1/P2] | [Brief detail of functionality] |
| FR-02 | [Feature Name] | [P0/P1/P2] | [Brief detail of functionality] |

## 3. Non-Functional Requirements (NFR)

- **Performance:** [e.g., System response time, uptime targets.]
- **Scalability:** [e.g., Expected user growth, data volume.]
- **Security:** [e.g., Encryption standards, authentication methods.]
- **Compliance:** [e.g., GDPR, HIPAA, or local regulations.]

## 4. User Journey Summary

[A 2-3 sentence overview of the primary path a user takes through the app.]

## 5. Out of Scope

[Explicitly list what the app will NOT do in this version to avoid scope creep.]