Files

Deploy to Production / Build and Deploy (push) Successful in 12s

Details

feat: design system overhaul — sidebar, AI chats, settings, brainstorm, color cleanup

- Sidebar: dynamic brand-accent colors, brainstorm section restyled
- AI chat general: popup panel with expand/collapse, hides when contextual AI open
- AI chat contextual: tabs reordered (Actions first), X close button, height fix
- Settings: all tabs restyled, 6 new color presets (sage, terracotta, iron, etc.)
- Global color cleanup: emerald/orange hardcoded → brand-accent dynamic
- Brainstorm page: orange → brand-accent throughout
- PageEntry animation component added to key pages
- Floating AI button: bg-brand-accent instead of hardcoded black
- i18n: all 15 locales updated with new AI/billing keys
- Billing: freemium quota tracking, BYOK, stripe subscription scaffolding
- Admin: integrated into new design
- AGENTS.md + CLAUDE.md project rules added

2026-05-16 12:59:30 +00:00

3.0 KiB

Raw Blame History

name, description

name	description
wds-5-agentic-development	AI-assisted development, testing, and reverse engineering through structured agent collaboration

Phase 5: Agentic Development

Goal: AI-assisted software development, testing, analysis, and reverse engineering through structured agent collaboration.

Your Role: Implementation partner guiding structured development activities with clear feedback protocols and approval gates.

WORKFLOW ARCHITECTURE

Phase 5 is menu-driven, not linear. The user picks an activity.

Core Principles

Activity-Based: Pick the right activity for the current need
Non-Linear: Start anywhere, switch between activities freely
Design Log Driven: Every activity reads/updates the design log for state tracking
Specification as Truth: All work traces back to approved specifications

Step Processing Rules

READ COMPLETELY: Always read the entire step file before taking any action
FOLLOW SEQUENCE: Execute all sections in order within a step
WAIT FOR INPUT: Halt at menus and wait for user selection
SAVE STATE: Update design log when completing steps

INITIALIZATION

1. Configuration Loading

Load and read full config from {project-root}/_bmad/wds/config.yaml and resolve:

project_name, output_folder, user_name
communication_language, document_output_language

2. Design Log

Read {output_folder}/_progress/00-design-log.md. Check Current and Backlog for context.

Present:

What would you like to do?

[P] Prototyping            — Build interactive prototype from specs
[D] Development            — Write production code
[F] Bugfixing              — Fix bugs in existing code
[E] Evolution              — Add features to existing product
[A] Analysis               — Understand your own codebase
[R] Reverse Engineering    — Any software/site → specs & extraction
[T] Acceptance Testing     — Design & run tests from spec criteria

Activity Routing

Choice	Workflow File	Steps Folder
[P]	workflow-prototyping.md	steps-p/
[D]	workflow-development.md	steps-d/
[F]	workflow-bugfixing.md	steps-f/
[E]	workflow-evolution.md	steps-e/
[A]	workflow-analysis.md	steps-a/
[R]	workflow-reverse-engineering.md	steps-r/
[T]	workflow-acceptance-testing.md	steps-t/

REFERENCE CONTENT

Location	Purpose
`data/guides/`	Development guides, protocols, analysis
`data/testing-guide.md`	Acceptance testing guide
`data/test-result-templates.md`	Test result templates
`data/issue-templates.md`	Issue reporting templates
`templates/`	Page, story, work file, roadmap templates

OUTPUT

Activity-specific output in project structure.

AFTER COMPLETION

Each activity workflow has its own explicit design log reporting points. See the individual workflow files for details on what to log and where.

3.0 KiB Raw Blame History