SDLC — Development Process

How WardrobeAI development works: branches, reviews, and releases.

Workflow

1. Issue Created ─→ Issue labeled (market/feature/engineering/business/legal)
                         │
                         ▼
2. Branch Created ─── feature/<short-description>
                         │
                         ▼
3. Pull Request Opened ──→ Auto-assigns reviewers
                         │
                         ▼
4. Review Gates ────────────────────────────────┐
    @engineering (code quality, architecture)    │
    @trust       (security, validation)          │ ALL must
    @market      (product requirements)          │ pass
                                                 │
    Each reviewer: approve or block with notes───┘
                         │
                         ▼
5. @cos Final Approval ───→ Merge to main
                         │
                         ▼
6. Issue Closed

Review Gates

1. @engineering — Code Quality & Architecture

Code follows project conventions
No unnecessary complexity
Test coverage is adequate
Performance considerations addressed

2. @trust — Security Review

Input validation and sanitization
SQL injection prevention (parameterized queries)
XSS prevention (React auto-escaping sufficient for now)
No hardcoded secrets, tokens, or credentials
API security (rate limiting, auth — when implemented)

3. @market — Product Review

Feature matches requirements in the issue
User experience is intuitive
Business logic is correct
Amazon affiliate integration is correct (when applicable)

4. @cos — Final Approval

All previous gates passed
Cross-functional consensus
Merge gate control

Branch Strategy

Branch	Purpose	Protection
`main`	Production code	Protected — no direct commits
`feature/*`	Feature work	From main, merged via PR
`fix/*`	Bug fixes	From main, merged via PR

Branch Naming

feature/<short-description> — e.g., feature/mvp-core, feature/amazon-affiliate
fix/<issue-description> — e.g., fix/hardcoded-preferences

Commit Signing

All commits must be signed. See issue #32 for setup.

# Configure signing
git config --local commit.gpgsign true
git config --local gpg.format ssh
git config --local user.signingkey ~/.ssh/wardrobe-ai-signing

# Commit with signature
git commit -S -m "feat: description"

Issue Labels

Label	Purpose
`market`	Market research, competitive analysis, customer personas
`feature`	Product features and design
`engineering`	Technical implementation and architecture
`business`	Pricing, financials, vendor partnerships
`legal`	Compliance, terms, policies
`improvement`	Documentation and process improvements

Project Phases (Milestones)

Issues are organized by milestone phases:

Phase 0: Foundation — Current phase
Phase 1: MVP — Next (May-Jul 2026)
Phase 2: Growth
Phase 3: Scale
Phase 4: Expansion

See the Roadmap for detailed phase information.

Agent Responsibilities

Agent	Role	Review Responsibility
`@engineering`	Builder	Code quality, architecture
`@trust`	Security	Security review
`@market`	Product	Product requirements, business logic
`@cos`	Coordinator	Final approval, merge control