What problem does it solve?
Turning a vague feature idea into a concrete, implementation-ready design specification is hard: requirements are missing, scope is unclear, and acceptance criteria are vague. This Skill elicits missing requirements, structures the design, and writes a spec developers can use for planning and implementation.
Core Features & Use Cases
- Requirements Elicitation: Asks targeted clarifying questions about users, scope, constraints, and success criteria, or records explicit assumptions when answers are unavailable.
- Structured Spec Generation: Produces a design document covering goals, non-goals, functional and non-functional requirements, architecture, data models, interfaces, risks, and testable acceptance criteria.
- Persistent Design Artifacts: Writes the finished spec to
.stencila/designs/{name}.md so it can be updated and reused across planning sessions.
- Use Case: Given a prompt like "design a feature for scheduling social media posts", the Skill produces a scoped spec with timezone handling constraints, platform API limits, and acceptance criteria for scheduling, validation, and failure handling.
Quick Start
Ask the assistant to create a software design specification for your feature idea, such as designing an internal tool for tracking lab equipment usage.
