@zigrivers/scaffold 2.1.0

package/pipeline/planning/review-tasks.md

@@ -0,0 +1,38 @@
+---
+name: review-tasks
+description: Review implementation tasks for coverage and feasibility
+phase: "planning"
+order: 26
+dependencies: [implementation-tasks]
+outputs: [docs/reviews/review-tasks.md]
+conditional: null
+knowledge-base: [review-methodology, review-implementation-tasks]
+---
+
+## Purpose
+Review implementation tasks targeting task-specific failure modes: architecture
+coverage gaps, missing dependencies, tasks too large or too vague for agents,
+critical path inaccuracy, and invalid parallelization assumptions.
+
+## Inputs
+- docs/implementation-tasks.md (required) — tasks to review
+- docs/system-architecture.md (required) — for coverage checking
+- docs/domain-models/ (required) — for completeness
+
+## Expected Outputs
+- docs/reviews/review-tasks.md — findings and resolution log
+- docs/implementation-tasks.md — updated with fixes
+
+## Quality Criteria
+- Architecture coverage verified (every component has tasks)
+- Dependency graph is valid DAG
+- No task is too large for a single agent session
+- Critical path is accurate
+- Parallelization assumptions are valid
+
+## Methodology Scaling
+- **deep**: Full multi-pass review. **mvp**: Coverage check only.
+- **custom:depth(1-5)**: Scale passes with depth.
+
+## Mode Detection
+Re-review mode if previous review exists.

package/pipeline/pre/create-prd.md

@@ -0,0 +1,45 @@
+---
+name: create-prd
+description: Create a product requirements document from a project idea
+phase: "pre"
+order: 1
+dependencies: []
+outputs: [docs/prd.md]
+conditional: null
+knowledge-base: [prd-craft]
+---
+
+## Purpose
+Transform a project idea into a structured product requirements document that
+defines the problem, target users, features, constraints, and success criteria.
+This is the foundation document that all subsequent phases reference.
+
+## Inputs
+- Project idea (provided by user verbally or in a brief)
+- Existing project files (if brownfield — any README, docs, or code)
+
+## Expected Outputs
+- docs/prd.md — Product requirements document
+
+## Quality Criteria
+- Problem statement is specific and testable (not vague aspirations)
+- Target users are identified with their needs
+- Features are scoped with clear boundaries (what's in, what's out)
+- Success criteria are measurable
+- Constraints (technical, timeline, budget, team) are documented
+- Non-functional requirements are explicit (performance, security, accessibility)
+
+## Methodology Scaling
+- **deep**: Comprehensive PRD. Competitive analysis, detailed user personas,
+  feature prioritization matrix (MoSCoW or similar), risk assessment, phased
+  delivery plan. 15-20 pages.
+- **mvp**: Problem statement, core features list, primary user description,
+  success criteria. 1-2 pages. Just enough to start building.
+- **custom:depth(1-5)**: Depth 1-2: MVP-style. Depth 3: add user personas
+  and feature prioritization. Depth 4-5: full competitive analysis and
+  phased delivery.
+
+## Mode Detection
+If docs/prd.md exists, operate in update mode: read existing content, identify
+what has changed or been learned since it was written, propose targeted updates.
+Preserve existing decisions unless explicitly revisiting them.

package/pipeline/pre/innovate-prd.md

@@ -0,0 +1,47 @@
+---
+name: innovate-prd
+description: Discover feature-level innovation opportunities in the PRD
+phase: "pre"
+order: 3
+dependencies: [review-prd]
+outputs: [docs/prd-innovation.md]
+conditional: "if-needed"
+knowledge-base: [prd-innovation, prd-craft]
+---
+
+## Purpose
+Discover feature-level innovation opportunities within the PRD. This covers
+new capabilities, competitive positioning, and defensive product gaps. It is
+NOT UX-level enhancement (that belongs in user story innovation) — it focuses
+on whether the right features are in the PRD at all.
+
+## Inputs
+- docs/prd.md (required) — PRD to analyze for innovation opportunities
+- docs/reviews/pre-review-prd.md (optional) — review findings for context
+
+## Expected Outputs
+- docs/prd-innovation.md — innovation findings, suggestions with cost/impact
+  assessment, and disposition (accepted/rejected/deferred)
+- docs/prd.md — updated with approved innovations
+
+## Quality Criteria
+- Enhancements are feature-level, not UX-level polish
+- Each suggestion has a cost estimate (trivial/moderate/significant)
+- Each suggestion has a clear user benefit and impact assessment
+- Approved innovations are documented to the same standard as existing features
+- PRD scope boundaries are respected — no uncontrolled scope creep
+- User approval is obtained before modifying the PRD
+
+## Methodology Scaling
+- **deep**: Full innovation pass across all categories (competitive research,
+  UX gaps, AI-native opportunities, defensive product thinking). Cost/impact
+  matrix. Detailed integration of approved innovations into PRD.
+- **mvp**: Not applicable — this step is conditional and skipped in MVP.
+- **custom:depth(1-5)**: Depth 1-2: not typically enabled. Depth 3: quick scan
+  for obvious gaps and missing expected features. Depth 4-5: full innovation
+  pass with evaluation framework.
+
+## Mode Detection
+If docs/prd-innovation.md exists, this is a re-innovation pass. Read previous
+suggestions and their disposition (accepted/rejected/deferred), focus on new
+opportunities from PRD changes since last run.

package/pipeline/pre/innovate-user-stories.md

@@ -0,0 +1,47 @@
+---
+name: innovate-user-stories
+description: Discover UX-level enhancements and innovation opportunities in user stories
+phase: "pre"
+order: 6
+dependencies: [review-user-stories]
+outputs: [docs/user-stories-innovation.md]
+conditional: "if-needed"
+knowledge-base: [user-stories, user-story-innovation]
+---
+
+## Purpose
+Discover UX-level enhancements and innovation opportunities within the existing
+user stories. This is NOT feature-level innovation (that belongs in PRD
+innovation — `innovate-prd`) — it focuses on making existing features better
+through smart defaults,
+progressive disclosure, accessibility improvements, and AI-native capabilities.
+
+## Inputs
+- docs/user-stories.md (required) — stories to enhance
+- docs/prd.md (required) — PRD boundaries (innovation must not exceed scope)
+
+## Expected Outputs
+- docs/user-stories-innovation.md — innovation findings, suggestions with
+  cost/impact assessment, and disposition (accepted/rejected/deferred)
+- docs/user-stories.md — updated with approved enhancements
+
+## Quality Criteria
+- Enhancements are UX-level, not new features
+- Each suggestion has a cost estimate (trivial/moderate/significant)
+- Each suggestion has a clear user benefit
+- Approved enhancements are integrated into existing stories (not new stories)
+- PRD scope boundaries are respected — no scope creep
+
+## Methodology Scaling
+- **deep**: Full innovation pass across all three categories (high-value
+  low-effort, differentiators, defensive gaps). Cost/impact matrix.
+  Detailed integration of approved enhancements into stories.
+- **mvp**: Not applicable — this step is conditional and skipped in MVP.
+- **custom:depth(1-5)**: Depth 1-2: not typically enabled. Depth 3: quick
+  scan for obvious improvements. Depth 4-5: full innovation pass with
+  evaluation framework.
+
+## Mode Detection
+If docs/user-stories-innovation.md exists, this is a re-innovation pass. Read
+previous suggestions and their disposition (accepted/rejected), focus on new
+opportunities from story changes since last run.

package/pipeline/pre/review-prd.md

@@ -0,0 +1,44 @@
+---
+name: review-prd
+description: Multi-pass review of the PRD for completeness, clarity, and downstream readiness
+phase: "pre"
+order: 2
+dependencies: [create-prd]
+outputs: [docs/reviews/pre-review-prd.md]
+conditional: null
+knowledge-base: [review-methodology, review-prd, prd-craft, gap-analysis]
+---
+
+## Purpose
+Deep multi-pass review of the PRD, targeting the specific failure modes of
+product requirements artifacts. Identify issues, create a fix plan, execute
+fixes, and re-validate. Ensures the PRD is complete, clear, consistent, and
+ready for User Stories to consume.
+
+## Inputs
+- docs/prd.md (required) — PRD to review
+- Project idea or brief (context from user, if available)
+
+## Expected Outputs
+- docs/reviews/pre-review-prd.md — review findings, fix plan, and resolution log
+- docs/prd.md — updated with fixes
+
+## Quality Criteria
+- All review passes executed with findings documented
+- Every finding categorized by severity (P0-P3)
+- Fix plan created for P0 and P1 findings
+- Fixes applied and re-validated
+- Downstream readiness confirmed (User Stories can proceed)
+
+## Methodology Scaling
+- **deep**: All 8 review passes from the knowledge base. Full findings report
+  with severity categorization. Fixes applied and re-validated.
+- **mvp**: Passes 1-2 only (Problem Statement Rigor, Persona Coverage). Focus
+  on blocking gaps — requirements too vague to write stories from.
+- **custom:depth(1-5)**: Depth 1-2: passes 1-2 only (Problem Statement Rigor,
+  Persona Coverage). Depth 3: passes 1-4 (add Feature Scoping, Success
+  Criteria). Depth 4-5: all 8 passes.
+
+## Mode Detection
+If docs/reviews/pre-review-prd.md exists, this is a re-review. Read previous
+findings, check which were addressed, run review passes again on updated PRD.

package/pipeline/pre/review-user-stories.md

@@ -0,0 +1,43 @@
+---
+name: review-user-stories
+description: Multi-pass review of user stories for PRD coverage, quality, and downstream readiness
+phase: "pre"
+order: 5
+dependencies: [user-stories]
+outputs: [docs/reviews/pre-review-user-stories.md]
+conditional: null
+knowledge-base: [review-methodology, review-user-stories]
+---
+
+## Purpose
+Deep multi-pass review of user stories, targeting failure modes specific to
+story artifacts. Identify coverage gaps, quality issues, and downstream
+readiness problems. Create a fix plan, execute fixes, and re-validate.
+
+## Inputs
+- docs/user-stories.md (required) — stories to review
+- docs/prd.md (required) — source requirements for coverage checking
+
+## Expected Outputs
+- docs/reviews/pre-review-user-stories.md — review findings, fix plan, and resolution log
+- docs/user-stories.md — updated with fixes
+
+## Quality Criteria
+- All review passes executed with findings documented
+- Every finding categorized by severity (P0-P3)
+- Fix plan created for P0 and P1 findings
+- Fixes applied and re-validated
+- Downstream readiness confirmed (modeling phase can proceed)
+
+## Methodology Scaling
+- **deep**: All 6 review passes from the knowledge base. Full findings report
+  with severity categorization. Fixes applied and re-validated.
+- **mvp**: Pass 1 only (PRD coverage). Focus on blocking gaps — PRD features
+  with no corresponding story.
+- **custom:depth(1-5)**: Depth 1: pass 1 only. Depth 2: passes 1-2.
+  Depth 3: passes 1-4. Depth 4-5: all 6 passes.
+
+## Mode Detection
+If docs/reviews/pre-review-user-stories.md exists, this is a re-review. Read
+previous findings, check which were addressed, run review passes again on
+updated stories.

package/pipeline/pre/user-stories.md

@@ -0,0 +1,48 @@
+---
+name: user-stories
+description: Translate PRD features into user stories with acceptance criteria
+phase: "pre"
+order: 4
+dependencies: [review-prd]
+outputs: [docs/user-stories.md]
+conditional: null
+knowledge-base: [user-stories]
+---
+
+## Purpose
+Translate PRD features and requirements into user stories that define user-facing
+behavior. Each story captures who wants what and why, with acceptance criteria
+that are testable and specific enough to drive domain modeling, UX design, and
+task decomposition downstream.
+
+## Inputs
+- docs/prd.md (required) — features, personas, and requirements to translate
+- docs/reviews/pre-review-prd.md (optional) — review findings for context
+- docs/prd-innovation.md (optional) — innovation findings and approved enhancements
+
+## Expected Outputs
+- docs/user-stories.md — user stories organized by epic, each with acceptance
+  criteria scaled to the configured depth level
+
+## Quality Criteria
+- Every PRD feature maps to at least one user story
+- Stories follow INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable)
+- Acceptance criteria are testable — unambiguous pass/fail
+- No story too large to implement in 1-3 focused agent sessions
+- Every PRD persona is represented in at least one story
+- Stories describe user behavior, not implementation details
+
+## Methodology Scaling
+- **deep**: Full story template with IDs, persona journey maps, cross-story
+  dependency graphs, Given/When/Then acceptance criteria with parameterized
+  examples, story-to-domain-event mapping for domain modeling consumption.
+- **mvp**: Flat list of one-liner stories grouped by PRD section. One bullet
+  per story for the primary success condition. No epics, no scope boundaries.
+- **custom:depth(1-5)**: Depth 1-2: flat list with brief acceptance criteria.
+  Depth 3: full template with IDs, epics, Given/When/Then. Depth 4-5: add
+  dependency mapping, traceability, UI/UX notes, story splitting rationale.
+
+## Mode Detection
+If docs/user-stories.md exists, operate in update mode: read existing stories,
+identify changes needed based on updated PRD, categorize as ADD/RESTRUCTURE/
+PRESERVE, get approval before modifying. Preserve existing story IDs.

package/pipeline/quality/operations.md

@@ -0,0 +1,42 @@
+---
+name: operations
+description: Define operations, deployment, and dev environment strategy
+phase: "quality"
+order: 21
+dependencies: [review-testing]
+outputs: [docs/operations-runbook.md]
+conditional: null
+knowledge-base: [operations-runbook]
+---
+
+## Purpose
+Define the operational strategy: CI/CD pipeline, deployment approach, monitoring
+and alerting, incident response, rollback procedures, and dev environment setup.
+This is both the production operations guide and the local development workflow.
+
+## Inputs
+- docs/system-architecture.md (required) — what to deploy
+- docs/testing-strategy.md (required) — CI pipeline test stages
+- docs/adrs/ (required) — infrastructure decisions
+
+## Expected Outputs
+- docs/operations-runbook.md — operations and deployment runbook
+
+## Quality Criteria
+- CI/CD pipeline defined with all stages (build, test, lint, deploy)
+- Deployment strategy chosen with rollback procedure
+- Monitoring covers key metrics (latency, error rate, saturation)
+- Alerting thresholds are justified, not arbitrary
+- Dev environment setup is documented and reproducible
+- Incident response process defined
+
+## Methodology Scaling
+- **deep**: Full runbook. Deployment topology diagrams. Monitoring dashboard
+  specs. Alert playbooks. DR plan. Capacity planning. Local dev with
+  containers matching production.
+- **mvp**: Basic CI/CD pipeline. Deploy command. How to run locally.
+- **custom:depth(1-5)**: Depth 1-2: MVP-style. Depth 3: add monitoring and
+  alerts. Depth 4-5: full runbook with DR.
+
+## Mode Detection
+Update mode if runbook exists.

package/pipeline/quality/review-operations.md

@@ -0,0 +1,37 @@
+---
+name: review-operations
+description: Review operations runbook for completeness and safety
+phase: "quality"
+order: 22
+dependencies: [operations]
+outputs: [docs/reviews/review-operations.md]
+conditional: null
+knowledge-base: [review-methodology, review-operations]
+---
+
+## Purpose
+Review operations runbook targeting operations-specific failure modes: deployment
+strategy gaps, missing rollback procedures, monitoring blind spots, unjustified
+alerting thresholds, missing runbook scenarios, and DR coverage gaps.
+
+## Inputs
+- docs/operations-runbook.md (required) — runbook to review
+- docs/system-architecture.md (required) — for deployment coverage
+
+## Expected Outputs
+- docs/reviews/review-operations.md — findings and resolution log
+- docs/operations-runbook.md — updated with fixes
+
+## Quality Criteria
+- Deployment lifecycle fully documented (deploy, verify, rollback)
+- Monitoring covers all critical metrics
+- Alert thresholds have rationale
+- Common failure scenarios have runbook entries
+- Dev environment parity assessed
+
+## Methodology Scaling
+- **deep**: Full multi-pass review. **mvp**: Deployment coverage only.
+- **custom:depth(1-5)**: Scale passes with depth.
+
+## Mode Detection
+Re-review mode if previous review exists.

package/pipeline/quality/review-security.md

@@ -0,0 +1,40 @@
+---
+name: review-security
+description: Review security review for coverage and correctness
+phase: "quality"
+order: 24
+dependencies: [security]
+outputs: [docs/reviews/review-security.md]
+conditional: null
+knowledge-base: [review-methodology, review-security]
+---
+
+## Purpose
+Review security review targeting security-specific failure modes: OWASP coverage
+gaps, auth/authz boundary mismatches with API contracts, secrets management gaps,
+insufficient dependency audit coverage, missing threat model scenarios, and data
+classification gaps.
+
+## Inputs
+- docs/security-review.md (required) — security review document
+- docs/api-contracts.md (optional) — for auth boundary alignment
+- docs/system-architecture.md (required) — for attack surface coverage
+
+## Expected Outputs
+- docs/reviews/review-security.md — findings and resolution log
+- docs/security-review.md — updated with fixes
+
+## Quality Criteria
+- OWASP coverage verified for this project
+- Auth boundaries match API contract auth requirements
+- Secrets management is complete (no gaps)
+- Dependency audit scope covers all dependencies
+- Threat model covers all trust boundaries
+- Data classification is complete
+
+## Methodology Scaling
+- **deep**: Full multi-pass review. **mvp**: OWASP coverage check only.
+- **custom:depth(1-5)**: Scale passes with depth.
+
+## Mode Detection
+Re-review mode if previous review exists.

package/pipeline/quality/review-testing.md

@@ -0,0 +1,39 @@
+---
+name: review-testing
+description: Review testing strategy for coverage gaps and feasibility
+phase: "quality"
+order: 20
+dependencies: [testing-strategy]
+outputs: [docs/reviews/review-testing.md]
+conditional: null
+knowledge-base: [review-methodology, review-testing-strategy]
+---
+
+## Purpose
+Review testing strategy targeting testing-specific failure modes: coverage gaps
+by layer, missing edge cases from domain invariants, unrealistic test environment
+assumptions, inadequate performance test coverage, and missing integration boundaries.
+
+## Inputs
+- docs/testing-strategy.md (required) — strategy to review
+- docs/domain-models/ (required) — for invariant test case coverage
+- docs/system-architecture.md (required) — for layer coverage
+
+## Expected Outputs
+- docs/reviews/review-testing.md — findings and resolution log
+- docs/testing-strategy.md — updated with fixes
+
+## Quality Criteria
+- Coverage gaps by layer identified
+- Domain invariant test cases verified
+- Test environment assumptions validated
+- Performance test coverage assessed against NFRs
+- Integration boundaries have integration tests defined
+
+## Methodology Scaling
+- **deep**: Full multi-pass review targeting all testing failure modes.
+- **mvp**: Coverage gap check only.
+- **custom:depth(1-5)**: Scale passes with depth.
+
+## Mode Detection
+Re-review mode if previous review exists.

package/pipeline/quality/security.md

@@ -0,0 +1,44 @@
+---
+name: security
+description: Security review and documentation
+phase: "quality"
+order: 23
+dependencies: [review-operations]
+outputs: [docs/security-review.md]
+conditional: null
+knowledge-base: [security-review]
+---
+
+## Purpose
+Conduct a security review of the entire system design. Document security
+controls, threat model, auth/authz approach, data protection, secrets
+management, and dependency audit strategy.
+
+## Inputs
+- docs/system-architecture.md (required) — attack surface
+- docs/api-contracts.md (optional) — auth/authz boundaries
+- docs/database-schema.md (optional) — data protection needs
+- docs/operations-runbook.md (required) — secrets and deployment security
+
+## Expected Outputs
+- docs/security-review.md — security review and controls document
+
+## Quality Criteria
+- OWASP top 10 addressed for this specific project
+- Auth/authz boundaries defined and consistent with API contracts
+- Data classified by sensitivity with handling requirements
+- Secrets management strategy defined (no secrets in code)
+- Threat model covers all trust boundaries
+- Dependency audit integrated into CI
+
+## Methodology Scaling
+- **deep**: Full threat model (STRIDE). OWASP analysis per component.
+  Data classification matrix. Secrets rotation plan. Penetration testing
+  scope. Compliance checklist (if applicable).
+- **mvp**: Key security controls. Auth approach. No secrets in code.
+  Basic input validation strategy.
+- **custom:depth(1-5)**: Depth 1-2: MVP-style. Depth 3: add threat model.
+  Depth 4-5: full security review.
+
+## Mode Detection
+Update mode if review exists.

package/pipeline/quality/testing-strategy.md

@@ -0,0 +1,42 @@
+---
+name: testing-strategy
+description: Define testing and quality strategy across all layers
+phase: "quality"
+order: 19
+dependencies: [review-architecture]
+outputs: [docs/testing-strategy.md]
+conditional: null
+knowledge-base: [testing-strategy]
+---
+
+## Purpose
+Define the testing strategy: test pyramid, coverage goals per layer, testing
+patterns, quality gates, and performance testing approach. This tells agents
+how to test the code they write.
+
+## Inputs
+- docs/system-architecture.md (required) — layers to test
+- docs/domain-models/ (required) — business rules to verify
+- docs/adrs/ (required) — testing technology choices
+- docs/api-contracts.md (optional) — API test scenarios
+- docs/database-schema.md (optional) — data layer test scenarios
+
+## Expected Outputs
+- docs/testing-strategy.md — testing approach with coverage goals and patterns
+
+## Quality Criteria
+- Test pyramid defined with coverage targets per layer
+- Testing patterns specified for each layer (unit, integration, e2e)
+- Quality gates defined (what must pass before merge)
+- Edge cases from domain invariants are test scenarios
+- Performance testing approach for critical paths
+
+## Methodology Scaling
+- **deep**: Comprehensive strategy. Test matrix by layer and component. Specific
+  test patterns per architecture pattern. Performance benchmarks. CI integration.
+  Test data strategy. Mutation testing approach.
+- **mvp**: Test pyramid overview. Key testing patterns. What must pass before deploy.
+- **custom:depth(1-5)**: Scale detail with depth.
+
+## Mode Detection
+Update mode if strategy exists.

package/pipeline/specification/api-contracts.md

@@ -0,0 +1,44 @@
+---
+name: api-contracts
+description: Specify API contracts for all system interfaces
+phase: "specification"
+order: 15
+dependencies: [review-architecture]
+outputs: [docs/api-contracts.md]
+conditional: "if-needed"
+knowledge-base: [api-design]
+---
+
+## Purpose
+Define API contracts for all system interfaces — REST endpoints, GraphQL schema,
+WebSocket events, or inter-service communication. Each endpoint specifies request/
+response shapes, error codes, authentication requirements, and rate limits.
+
+## Inputs
+- docs/system-architecture.md (required) — component interfaces to specify
+- docs/domain-models/ (required) — domain operations to expose
+- docs/adrs/ (required) — API style decisions (REST vs GraphQL, versioning)
+
+## Expected Outputs
+- docs/api-contracts.md — API specification with endpoints, request/response
+  shapes, error contracts, auth requirements
+
+## Quality Criteria
+- Every domain operation that crosses a component boundary has an API endpoint
+- Error contracts are explicit (not just "500 Internal Server Error")
+- Authentication and authorization requirements per endpoint
+- Versioning strategy documented (if applicable)
+- Pagination, filtering, and sorting for list endpoints
+- Idempotency documented for mutating operations
+
+## Methodology Scaling
+- **deep**: OpenAPI-style specification. Full request/response schemas with
+  examples. Error catalog. Auth flow diagrams. Rate limiting strategy.
+  SDK generation considerations.
+- **mvp**: Endpoint list with HTTP methods and brief descriptions. Key
+  request/response shapes. Auth approach.
+- **custom:depth(1-5)**: Depth 1-2: endpoint list. Depth 3: add schemas and
+  error contracts. Depth 4-5: full OpenAPI-style spec.
+
+## Mode Detection
+Update mode if contracts exist. Diff against architecture changes.

package/pipeline/specification/database-schema.md

@@ -0,0 +1,41 @@
+---
+name: database-schema
+description: Design database schema from domain models
+phase: "specification"
+order: 13
+dependencies: [review-architecture]
+outputs: [docs/database-schema.md]
+conditional: "if-needed"
+knowledge-base: [database-design]
+---
+
+## Purpose
+Translate domain models into a concrete database schema. Define tables/collections,
+relationships, indexes, constraints, and migration strategy.
+
+## Inputs
+- docs/domain-models/ (required) — entities and relationships to model
+- docs/system-architecture.md (required) — data layer architecture decisions
+- docs/adrs/ (required) — technology choices (database type, ORM)
+
+## Expected Outputs
+- docs/database-schema.md — schema design with tables, relationships, indexes,
+  constraints, and migration strategy
+
+## Quality Criteria
+- Every domain entity maps to a table/collection (or justified denormalization)
+- Relationships match domain model relationships
+- Indexes cover known query patterns from architecture data flows
+- Constraints enforce domain invariants at the database level
+- Migration strategy handles schema evolution
+
+## Methodology Scaling
+- **deep**: Full schema specification. CREATE TABLE statements or equivalent.
+  Index justification with query patterns. Normalization analysis. Migration
+  plan with rollback strategy. Seed data strategy.
+- **mvp**: Entity-to-table mapping. Key relationships. Primary indexes only.
+- **custom:depth(1-5)**: Depth 1-2: mapping only. Depth 3: add indexes and
+  constraints. Depth 4-5: full specification with migrations.
+
+## Mode Detection
+Update mode if schema exists. Diff against current domain models.