wisedev-suite

enforce wisedev workflow discipline before product-delivery tasks. use when the user asks for requirement clarification, requirement specifications, design documents, openapi yaml contracts, vue plus mock prototypes, or any request that may cross stages. require the assistant to check the wisedev skill suite first, route multi-stage tasks through wisedev-orchestrator first, and map clear single-stage requests to the correct wisedev child skill.

orchestrate staged delivery artifact generation from short requirements, meeting notes, transcripts, and mixed materials. use when the user wants to turn ambiguous chinese product or business input into structured outputs such as requirement briefs, requirement specifications, design documents, openapi yaml contracts, or vue plus mock prototypes. act as the mandatory entry skill for multi-stage work: identify the current stage first, normalize context first, choose one child skill first, and require stage handoff artifacts before any downstream stage.

generate vue-based frontend prototype plans and code scaffolds with local mock services from chinese requirement, design, and openapi artifacts. use when the user needs a modern vue 3 plus vite plus typescript plus pinia plus router prototype, with realistic mock data, workflow states, and local run instructions for complex enterprise business demonstrations.

recommend contrasting prototype design directions, generate theme token packages, and critique visual outputs for chinese enterprise-facing prototypes. use when the user needs design direction, visual style comparison, color schemes, prototype themes, or design review before or after vue prototype generation.

generate chinese high-level and detailed design documents from requirement specifications, requirement briefs, or structured business input. use when the user needs architecture decomposition, module boundaries, role permissions, workflows, state transitions, data entities, interfaces, and exception handling documented in markdown in a formal enterprise style.

analyze meeting notes, transcript text, and mixed chinese discussion materials and convert them into structured requirement inputs. use when the user provides a transcript, a meeting summary, or scattered discussion text and wants requirement clarification, feature extraction, role and scenario analysis, unresolved question tracking, or a draft requirement brief.

generate openapi yaml contracts from requirement and design artifacts. use when the user needs chinese business requirements converted into mock-ready api paths, request and response schemas, error models, pagination, security, and example payloads in a single self-contained openapi yaml file.

write structured chinese requirement specifications from rough needs, clarified requirement briefs, transcripts, or mixed materials. use when the user needs a formal markdown requirement document with scope, actors, scenarios, functional requirements, non-functional requirements, acceptance criteria, and traceable identifiers in a government or enterprise documentation style.