Requirements Baseline:
- Total FRs: {count}
- Total NFRs: {count}
- Critical FRs (Must Have): {count}
- Epics (if PRD): {count}

### Functional Requirements Coverage

**Total FRs:** {total}
**Covered:** {covered_count} ({percentage}%)
**Missing:** {missing_count}

**Missing FRs:**
{list of FRs not addressed in architecture}

**Partial Coverage (needs clarification):**
{list of FRs with incomplete coverage}

### Non-Functional Requirements Coverage

**Total NFRs:** {total}
**Fully Addressed:** {full_count} ({percentage}%)
**Partially Addressed:** {partial_count} ({percentage}%)
**Missing:** {missing_count}

**Missing NFRs:**
{list of NFRs not addressed}

**Needs Improvement:**
{list of NFRs with weak or generic solutions}

### Architecture Quality Checklist

**System Design:**
- [ ] Architectural pattern is clearly stated and justified
- [ ] System components are well-defined (3-10 components)
- [ ] Component responsibilities are clear
- [ ] Component interfaces are specified
- [ ] Dependencies between components are documented

**Technology Stack:**
- [ ] Frontend technology is selected and justified
- [ ] Backend framework is selected and justified
- [ ] Database choice is explained with rationale
- [ ] Infrastructure approach is defined
- [ ] Third-party services are identified
- [ ] Trade-offs are documented for major tech choices

**Data Architecture:**
- [ ] Core data entities are defined
- [ ] Entity relationships are specified
- [ ] Database design is described
- [ ] Data flow is documented
- [ ] Caching strategy is defined (if applicable)

**API Design:**
- [ ] API architecture is specified (REST, GraphQL, etc.)
- [ ] Key endpoints are listed (10-20 for Level 2, more for 3-4)
- [ ] Authentication method is defined
- [ ] Authorization approach is specified
- [ ] API versioning strategy is stated

**Security:**
- [ ] Authentication design is comprehensive
- [ ] Authorization model is defined
- [ ] Data encryption (at rest and in transit) is addressed
- [ ] Security best practices are documented
- [ ] Secrets management is addressed

**Scalability  &   Performance:**
- [ ] Scaling strategy is defined (horizontal/vertical)
- [ ] Performance optimization approaches are listed
- [ ] Caching strategy is comprehensive
- [ ] Load balancing is addressed

**Reliability:**
- [ ] High availability design is present
- [ ] Disaster recovery approach is defined
- [ ] Backup strategy is specified
- [ ] Monitoring and alerting are addressed

**Development  &   Deployment:**
- [ ] Code organization is described
- [ ] Testing strategy is defined (unit, integration, e2e)
- [ ] CI/CD pipeline is outlined
- [ ] Deployment strategy is specified
- [ ] Environments are defined (dev, staging, prod)

**Traceability:**
- [ ] FR-to-component mapping exists
- [ ] NFR-to-solution mapping exists
- [ ] Trade-offs are explicitly documented

**Completeness:**
- [ ] All major decisions have rationale ( " why " )
- [ ] Assumptions are stated
- [ ] Constraints are documented
- [ ] Risks are identified
- [ ] Open issues are listed

# Solutioning Gate Check Report
**Date:** {date}
**Project:** {project_name}
**Reviewer:** {user_name} (Winston - System Architect)
**Architecture Version:** {version}

---

## Executive Summary

**Overall Assessment:** {PASS | CONDITIONAL PASS | FAIL}

**Summary:**
{2-3 sentence summary of architecture quality and readiness}

**Key Findings:**
- {Finding 1}
- {Finding 2}
- {Finding 3}

---

## Requirements Coverage

### Functional Requirements
- **Total FRs:** {total}
- **Covered:** {covered} ({percentage}%)
- **Missing:** {missing}

{Details from Part 2}

### Non-Functional Requirements
- **Total NFRs:** {total}
- **Fully Addressed:** {full} ({percentage}%)
- **Partially Addressed:** {partial} ({percentage}%)
- **Missing:** {missing}

{Details from Part 3}

---

## Architecture Quality Assessment

**Score:** {passed}/{total} checks passed ({percentage}%)

{Failed checks with details}

---

## Critical Issues (if any)

**Blockers (must fix before proceeding):**
{list of critical gaps}

**Major Concerns (strongly recommend addressing):**
{list of significant issues}

**Minor Issues (nice to have):**
{list of minor improvements}

---

## Recommendations

{3-5 specific recommendations for improvement}

---

## Gate Decision

**Decision:** {PASS | CONDITIONAL PASS | FAIL}

**PASS Criteria:**
- ≥90% FR coverage
- ≥90% NFR coverage (fully or partially addressed)
- ≥80% quality checks passed
- No critical blockers

**CONDITIONAL PASS Criteria:**
- ≥80% FR coverage
- ≥80% NFR coverage
- ≥70% quality checks passed
- Blockers have mitigation plans

**FAIL Criteria:**
-  < 80% FR or NFR coverage
-  < 70% quality checks passed
- Critical blockers without mitigation

**Status:** {PASS/CONDITIONAL/FAIL}

**Rationale:** {why this decision}

**Conditions (if conditional pass):**
{list of items that must be addressed during implementation}

---

## Next Steps

{recommendations based on gate decision}

**If PASS:**
✓ Architecture approved! Proceed to Phase 4 (Implementation)

Next: Sprint Planning
Run /sprint-planning to:
- Break epics into detailed stories
- Estimate story complexity
- Plan sprint iterations
- Begin implementation

**If CONDITIONAL PASS:**
⚠ Architecture approved with conditions

You may proceed to implementation, but must address:
{list of conditions}

Review these items during sprint planning and early sprints.

**If FAIL:**
✗ Architecture needs significant work before implementation

Required actions:
{list of required improvements}

Re-run /solutioning-gate-check after addressing these issues.

---

## Appendix: Detailed Findings

{Full details of all checks, FR/NFR mappings, quality assessment}

---

**This report was generated using BMAD Method v6 - Phase 3 (Solutioning Gate)**

✓ Solutioning Gate Check Complete!

Architecture Assessment:
- FR Coverage: {percentage}%
- NFR Coverage: {percentage}%
- Quality Score: {percentage}%

Gate Decision: {PASS | CONDITIONAL PASS | FAIL}

{Brief rationale}

Full report: {file_path}

Excellent! Your architecture is solid and complete.

✓ Ready for Phase 4: Implementation

Next: Run /sprint-planning to:
- Break epics into detailed user stories
- Estimate story points
- Plan sprint iterations
- Begin development with confidence

Your planning documentation is complete:
✓ Product Brief
✓ PRD
✓ Architecture (validated)

Your architecture is approved with minor conditions.

⚠ Proceed to implementation, but track these items:
{list of conditions}

Next: Run /sprint-planning

Address conditions during early sprints.

Architecture needs improvement before implementation can begin.

Required actions:
{top 3-5 issues}

After addressing these:
1. Update architecture document
2. Re-run /solutioning-gate-check
3. Then proceed to /sprint-planning

Covered FRs = FRs with component assignments
Coverage % = (Covered / Total) * 100

Fully Addressed = NFRs with complete architectural solutions
Partially Addressed = NFRs mentioned but solution incomplete
Coverage % = ((Fully + Partial) / Total) * 100

Quality % = (Passed Checks / Total Checks) * 100