wds-5-agentic-development

Use the Prototyping activity, which sets up a prototype folder, analyzes the scenario into logical views, breaks each view into 4-8 sections, and implements each section from a just-in-time story file. Every section is verified with Puppeteer and approved by the user before continuing.

It includes seven activities: Prototyping, Development, Bugfixing, Evolution, Analysis, Reverse Engineering, and Acceptance Testing. Each has its own workflow file and ordered step files, all coordinated through a central design log.

Every activity reads and appends to a design log at 00-design-log.md in the output folder. Statuses such as building, built, and approved are recorded per page, and dated progress entries document analyses, fixes, and completed work.

Yes, the Reverse Engineering activity explores a target codebase or public website, captures patterns and inventory, then generates WDS-format page specifications and extracts design tokens. It explicitly avoids copying proprietary code or assets.

Use Bugfixing when existing code has a defect: it enforces reproduce-first, root-cause analysis, and regression checks. Use Evolution when adding new features to a working product, with impact analysis and backward-compatibility verification at each commit.