qiuzhi-skill-creator

To design a new agent skill, you must break down requirements into discovery, blueprint, and implementation phases to capture inputs, outputs, triggers, and architecture. This structured approach produces detailed blueprints, resource plans, and validation steps before any coding begins.

Using AskUserQuestion prompts during a discovery phase captures expected inputs, outputs, and triggers for new agent skills. This interactive SOP ensures nothing critical is missed by clarifying scope and technical approach before authoring the SKILL.md file.

A blueprint and validation plan enforce engineering discipline by confirming the architecture document, resource checklist, and testing plan before implementation. This prevents vague requests for new agent behaviors from turning into incomplete or flawed skills.

Yes, you can run an interactive SOP to capture goals, design the workflow, and confirm the roadmap before coding an agent skill that automates document workflows. This ensures the skill is fully specified through structured discovery and validation steps.

Yes, skill creation requires defining triggers, expected inputs, and outputs beforehand to fully scope the agent architecture. Capturing these elements during the discovery phase ensures the technical approach and resource plan are validated before implementation.