skills.rest
Miosa-osa
Miosa-osaOFFICIAL
Explore all skills by this author →
WebsiteGitHub

Spec

Draft technical specifications covering goals, requirements, architecture, and test plans.

226|55|Updated Mar 19, 2026
Search Tags:#architecture#documentation#collaboration#specification#requirements#spec#system-design
One-click install
npx skills add https://github.com/Miosa-osa/canopy --skill spec-miosa-osa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Spec
Source: https://github.com/Miosa-osa/canopy/tree/main/operations/dev-shop/skills/spec
Command: npx skills add https://github.com/Miosa-osa/canopy --skill spec-miosa-osa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafts comprehensive technical specifications for features or system changes to accelerate alignment and reduce ambiguity across product and engineering teams.

Core Features & Use Cases

  • Generates goals, requirements, constraints, architecture sections, and test plans.
  • Supports collaboration between tech-leads and architects to produce a single, coherent spec.
  • Useful for kickoff, design reviews, API contract drafting, and change-management.

Quick Start

Run /spec "user-login-feature" to generate a complete specification document.

Frequently Asked Questions about Spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I draft a technical specification for a new system feature?▼

To draft a technical specification, define the feature goals, requirements, constraints, and architecture. A complete spec also covers test plans and rollback strategies to reduce ambiguity across product and engineering teams during kickoff and design reviews.

What should be included in an API contract specification for architecture reviews?▼

An API contract specification should include goals, system requirements, constraints, and architecture details. It must also define test plans and rollback procedures to ensure technical alignment and reduce ambiguity during architecture and design reviews.

Can I use auto-generation to create complete feature specs for engineering teams?▼

Yes, you can auto-generate complete feature specs to accelerate alignment. This produces a coherent document covering goals, requirements, constraints, architecture, and test plans, supporting collaboration between tech-leads and architects.

Does a good system design spec need test and rollback plans?▼

Yes, a comprehensive system design spec requires both test and rollback plans. Including these sections ensures that engineering and architecture teams have a clear change-management strategy and can safely validate system modifications.

What is the best way to align product and engineering teams on requirements?▼

The best way to align teams is by drafting a comprehensive technical specification. It establishes a single, coherent document for goals, architecture, and constraints, enabling collaborative review and reducing ambiguity before system changes begin.

Related Skills

Explore More Software Engineering Skills→
thepriceisrightthepriceisright

prd

Generate a structured PRD from a feature brief and save it to tasks/prd-[feature-name].md.

Community
Advanced
scanbottscanbott

plan-eng-review

Review engineering execution plans for architecture, data flow, and testing.

Community
Advanced
acertainKnightacertainKnight
12

Skill Creation Workshop

Guide teams through a six-phase skill co-design workflow with structured templates.

Community
Basic
ryryoryryo
3

dev:ideation

Convert product ideas into structured specifications with JTBD analysis and SLC framing.

Community
Advanced