skills.rest
ewhauser
ewhauserCOMMUNITY
Explore all skills by this author →
Website𝕏@ewhauserGitHub

spec-writer

Draft and maintain technical design specifications with defined sections for architecture decisions.

106|3|Updated Apr 4, 2026
Search Tags:#design#architecture#documentation#specification#verification#product-design#team-alignment
One-click install
npx skills add https://github.com/ewhauser/shuck --skill spec-writer-ewhauser
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-writer
Source: https://github.com/ewhauser/shuck/tree/main/.claude/skills/spec-writer
Command: npx skills add https://github.com/ewhauser/shuck --skill spec-writer-ewhauser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear, consistent engineering decisions require living design specs that capture what we’re building, why it matters, and how we’ll verify success.

Core Features & Use Cases

  • Draft new specs for new features or systems, detailing the problem, proposed solution, success criteria, and risks.
  • Update existing specs to reflect changes in requirements, constraints, or implementation progress.
  • Align teams by enforcing project conventions and providing a transparent decision record that is easy to reference during reviews.

Quick Start

Draft a complete specification for the requested feature, following existing project conventions.

Frequently Asked Questions about spec-writer

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

FAQPage Schema
How do I write a technical specification for a new feature proposal?▼

To write a technical specification, draft sections for Summary, Motivation, Design, Alternatives Considered, Security, and Verification to detail what to build, why it matters, and how to verify success.

What is the best way to document architecture decisions for cross-team alignment?▼

Documenting architecture decisions requires a living design spec that captures the problem, proposed solution, success criteria, and risks, providing a transparent decision record that teams can easily reference during reviews.

How do I structure a design spec to ensure testable and reviewable commitments?▼

Structure a design spec by enforcing project conventions and specifying sections like Design and Verification, which ensure testable, reviewable commitments and support iterative updates as implementation progresses.

When do I need a design specification for a significant system refactor?▼

You need a design specification for a significant system refactor when you must align teams, apply project conventions, and capture what is changing, why it matters, and how to verify the results.

Can I update existing technical specifications to reflect changing requirements?▼

Yes, you can update existing technical specifications to reflect changes in requirements, constraints, or implementation progress, treating them as living documents that support iterative updates throughout the project lifecycle.

Related Skills

Explore More Design & Creative Skills→
dtsongdtsong
1

intake-skill

Transform natural language project descriptions into structured engagement briefs.

Community
Advanced
CodingCossackCodingCossack
19

subagent-driven-development

Executes sequential subagents with two-stage reviews for multi-task plans.

Community
Advanced
erikliebeneriklieben
7

doc-design

Generate technical design documentation with C4 diagrams and standardized templates.

Community
Intermediate
WayneWalterBerryWayneWalterBerry

project-conventions

Codify standard project conventions for code structure and documentation workflows.

Community
Basic