---

name: design-document-management description: Guide for managing the 5 design documents in .gaia/designs/. Use when creating, updating, or validating design documentation.

Design Document Management

Design Documents (in .gaia/designs/)

Tiered Requirements by SDLC

Quality Rules

• ✅ No [TODO] or [TBD] placeholders in required docs
• ✅ Consistent terminology across all docs
• ✅ Every requirement maps to a design section
• ✅ Follow Clean Architecture / iDesign principles

Completion Checklist

Before creating tasks, verify:

• All required docs for SDLC tier exist
• No template placeholders remain
• Designs capture 100% of requirements
• Entity names match across docs
• API paths consistent
• Database schema aligns with API contracts

Store Design Decisions

Copymcp__gaia__remember("design", "use-cases", "[user flows and journeys]", "ProjectWide")
mcp__gaia__remember("design", "architecture", "[key decisions]", "ProjectWide")
mcp__gaia__remember("design", "api", "[endpoint designs]", "ProjectWide")
mcp__gaia__remember("design", "database", "[schema decisions]", "ProjectWide")
mcp__gaia__remember("design", "security", "[auth approach]", "ProjectWide")
mcp__gaia__remember("design", "frontend", "[component patterns]", "ProjectWide")

Document Update Process

1. Identify which docs need updates based on requirements
2. Update each doc with new requirements
3. Cross-check consistency across all docs
4. Validate no placeholders remain
5. Store key decisions in MCP memory