✨ feat(aidd-dev): add a "generate-wireframes" action to the plan skill
Summary: Add a new action to the aidd-dev:01-plan skill that generates wireframes from a feature/requirements description, complementing the existing image-to-inventory flow.
🌟 Objective / Problem
The 01-plan skill today goes from requirements → technical plan, and from an existing design image → component inventory (03-image-extract-details). There is no path the other way: turning a textual feature description into a low-fidelity wireframe before any design exists. Planners have to imagine the UI layout in their head or jump straight to code.
🛠️ Proposed Solution
Add a new action (e.g. 04-wireframes-generate) to the 01-plan skill.
- Add
actions/04-wireframes-generate.md describing the action (inputs: feature description / user stories; output: wireframe artifact saved to a task/doc file).
- Register it in
SKILL.md: add a row to the actions table and a routing rule (a request to sketch/lay out/wireframe a UI → this action).
- Decide and document the wireframe output format (see constraints below).
- Update the skill
README.md accordingly.
🔍 Context / Technical Constraints (Optional)
- Output format is the key open decision: ASCII/box-drawing wireframes, HTML/CSS low-fi, SVG, or a Mermaid-based layout. Mermaid is poor at wireframes, so this likely needs a different medium than
02-components-behavior.
- Must respect the skill's
agent: planner / context: fork delegation model and the "plans/docs only, no code" boundary in docs/ARCHITECTURE.md.
- Should chain cleanly: wireframe →
01-plan, and ideally be the inverse of 03-image-extract-details.
📎 Attachments / References (Optional)
- Skill:
plugins/aidd-dev/skills/01-plan/
🙏 QA
SKILL.md lists the new action in the table and routing section.
- The action file exists and follows the structure of the sibling action files.
- Running the plan skill with a "wireframe this feature" request routes to the new action and produces a saved wireframe artifact.
✨ feat(aidd-dev): add a "generate-wireframes" action to the plan skill
🌟 Objective / Problem
The
01-planskill today goes from requirements → technical plan, and from an existing design image → component inventory (03-image-extract-details). There is no path the other way: turning a textual feature description into a low-fidelity wireframe before any design exists. Planners have to imagine the UI layout in their head or jump straight to code.🛠️ Proposed Solution
Add a new action (e.g.
04-wireframes-generate) to the01-planskill.actions/04-wireframes-generate.mddescribing the action (inputs: feature description / user stories; output: wireframe artifact saved to a task/doc file).SKILL.md: add a row to the actions table and a routing rule (a request to sketch/lay out/wireframe a UI → this action).README.mdaccordingly.🔍 Context / Technical Constraints (Optional)
02-components-behavior.agent: planner/context: forkdelegation model and the "plans/docs only, no code" boundary indocs/ARCHITECTURE.md.01-plan, and ideally be the inverse of03-image-extract-details.📎 Attachments / References (Optional)
plugins/aidd-dev/skills/01-plan/🙏 QA
SKILL.mdlists the new action in the table and routing section.