Generate a technical design document from a feature spec — selects frameworks, defines data models, produces API contracts, and creates a dependency-ordered implementation strategy. Use when planning how to build a feature, writing a technical design doc, choosing libraries, defining database schemas, or setting up Tessl tiles for runtime library knowledge.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "iikit-02-plan" with this command: npx skills add JaviMontano/skillsmp-javimontano-javimontano-iikit-02-plan
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
Writes testable acceptance criteria in Given/When/Then format, covering happy paths, edge cases, and error scenarios. Trigger: "acceptance criteria", "given when then", "write AC", "define done", "user story criteria".
Contract-first API design producing OpenAPI specs, GraphQL schemas, or protobuf definitions with versioning strategy. Trigger: "design API", "OpenAPI spec", "GraphQL schema", "protobuf definition", "API contract".
Defines design tokens, component libraries, and page structures for consistent technical deliverables. Trigger: "design system", "design tokens", "component library", "page structure".
Logging architecture, distributed tracing, metrics design, alerting strategy, SLO/SLI definition, and incident response procedures. Trigger: "observability", "logging", "tracing", "metrics", "alerting", "SLO", "SLI", "incident response".