Orchestrate a gated design dialogue to produce an approved spec and design artifacts.
npx skills add https://github.com/Alexander-Tyagunov/magician --skill conjure
Please help me install this Agent Skill. Skill: conjure Source: https://github.com/Alexander-Tyagunov/magician/tree/main/skills/conjure Command: npx skills add https://github.com/Alexander-Tyagunov/magician --skill conjure
This skill streamlines the upfront design phase by enforcing a gated dialogue to lock in a spec and visual artifacts before any implementation work begins.
Initiate the gated design dialogue and respond to clarifying questions one turn at a time until the spec is approved.
High-intent search queries and answers about installing and using this skill.
A gated design dialogue is a structured workflow that extracts requirements and confirms constraints before coding begins. You need it when frontend, backend, or system architecture decisions must be locked and approved prior to implementation to prevent scope creep.
To generate an approved specification document and mockups, initiate a gated design workflow that drives a one-question-per-turn clarify loop to extract requirements and log decisions until the spec and visual artifacts are approved.
Yes, this structured design workflow supports frontend, backend, data, and architecture decisions across diverse tech stacks. It applies to any project where scope and UI decisions must be locked before implementation begins.
The best way to enforce a one-question-per-turn clarify loop is to use a gated design workflow that extracts requirements sequentially, logs decisions for traceability, and produces an approved spec before any implementation work starts.
The decision logging mechanism records architectural and scope decisions as they are confirmed during the one-turn-per-clarifying-question loop. This creates a traceable decision log that forms the foundation of the final approved specification document.
You should not use a gated design workflow if your project requires immediate implementation without upfront architectural decisions, or if the scope and UI decisions do not need to be formally locked and approved before coding begins.
Menschlichkeit-OsterreichGuide iterative dialogue to transform abstract ideas into detailed design specifications.
samibrahmiConvert approved mockups into production components with routing and dependency updates.
cptnfrenGuide one-question-per-turn dialogues with A-D options and rationale.
fumtas1kFacilitate structured brainstorming to develop designs and specifications through collaborative dialogue.
