claude-tweaks:specify

Decompose design documents into agent-sized specs with deliverables and acceptance criteria.

2|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/thomasholknielsen/claude-tweaks --skill claude-tweaks-specify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-tweaks:specify
Source: https://github.com/thomasholknielsen/claude-tweaks/tree/main/skills/specify
Command: npx skills add https://github.com/thomasholknielsen/claude-tweaks --skill claude-tweaks-specify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts brainstorming design documents into self-contained agent-sized specs, enabling structured planning and execution within the Claude-tweaks workflow.

Core Features & Use Cases

  • Decomposes a brainstorming design document into agent-sized specs suitable for build, test, and integration steps.
  • Produces self-contained specs with Deliverables, Acceptance Criteria, Prerequisites, and Manual Steps, ready for /claude-tweaks:build.
  • Preserves context and decisions by absorbing assumptions and constraints into each spec and mapping design ideas to actionable work units.

Quick Start

Provide the path to the design doc (for example, docs/plans/2026-02-21-meal-planning-design.md) and the skill will generate specs under specs/.

Frequently Asked Questions about claude-tweaks:specify

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

FAQPage Schema
How do I decompose a design doc into executable specifications for project management?

Design doc decomposition breaks brainstorming documents into self-contained, agent-sized specs. Each specification includes structured sections for Deliverables, Acceptance Criteria, Prerequisites, and Manual Steps to guide downstream build and validation.

What is the best way to turn brainstorming notes into actionable work units?

Turning brainstorming notes into actionable work units involves mapping design ideas to executable specs. This process preserves context and decisions by absorbing assumptions and constraints directly into each generated specification ready for build execution.

How do I structure project specifications for automated build and validation workflows?

Project specifications for automated workflows are structured using Deliverables, Acceptance Criteria, Prerequisites, and Manual Steps. This format ensures each spec is self-contained, enabling structured planning and execution within the build and test phases.

Do I need a specific design doc format to generate project management specs?

You need a markdown design document path, such as docs/plans/project-name-design.md, to generate project management specs. The skill reads the brainstorming document and outputs the resulting specifications directly under the specs directory.

When should I not use automated spec decomposition for my design documents?

Automated spec decomposition should not be used when a design document lacks sufficient detail for mapping to actionable work units. The process requires clear assumptions and constraints within the brainstorming notes to generate effective executable specifications.

Can I use these generated specifications independently outside of the claude-tweaks workflow?

Generated specifications include standard project management structures like Deliverables and Acceptance Criteria, making them usable independently. However, they are specifically formatted to be self-contained for seamless integration within the claude-tweaks build workflow.