skills.rest
kochetkov-ma
kochetkov-maCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

brewcode:spec

Generate SPEC.md technical specifications from codebase research and user interaction.

30|2|Updated Jan 24, 2026
Search Tags:#code analysis#documentation#software development#specification#requirements gathering#task planning
One-click install
npx skills add https://github.com/kochetkov-ma/claude-brewcode --skill brewcode-spec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brewcode:spec
Source: https://github.com/kochetkov-ma/claude-brewcode/tree/main/brewcode/skills/spec
Command: npx skills add https://github.com/kochetkov-ma/claude-brewcode --skill brewcode-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of detailed technical specifications for software development tasks, reducing ambiguity and ensuring all requirements are captured.

Core Features & Use Cases

  • Automated Research: Scans your codebase to understand existing patterns and identify relevant areas.
  • Interactive Clarification: Asks targeted questions to refine scope, constraints, and edge cases.
  • Structured Output: Generates a comprehensive SPEC.md document including architecture, risks, and decisions.
  • Use Case: When starting a new feature like "implementing a user profile service," this Skill will analyze your project, ask about data storage and API needs, and produce a detailed specification document.

Quick Start

Use the brewcode:spec skill to create a specification for building an authentication system with OAuth2 support.

Frequently Asked Questions about brewcode:spec

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

FAQPage Schema
How do I generate technical specifications for software development tasks?▼

To generate technical specifications, this Skill researches your codebase and asks targeted questions to identify scope, constraints, and edge cases, consolidating findings into a SPEC.md document.

What is the best way to document requirements gathering for a new feature?▼

The best way to document requirements gathering is using automated research and interactive clarification to capture architecture, risks, and decisions in a structured specification document.

Can I use this for code analysis to understand existing patterns before planning?▼

Yes, you can use this for code analysis because it scans your codebase to understand existing patterns and identify relevant areas before generating your task specification.

How does interactive clarification work when creating a task specification?▼

Interactive clarification works by asking targeted questions during the specification process to refine scope, constraints, and edge cases, ensuring all project requirements are accurately captured.

Does the output specification follow project-specific templates?▼

Yes, the output specification follows project-specific templates, ensuring the generated SPEC.md document aligns with your established formats and includes a review loop.

Related Skills

Explore More Software Engineering Skills→
solace-illsolace-ill

onboard

Generate role-specific onboarding documents from CLAUDE.md and agent definitions.

Community
Advanced
kjgarzakjgarza
3

detect-code-smells

Detect code smells and anti-patterns in source files using AST parsing and metrics-based scoring.

Community
Advanced
fmbetancourtfmbetancourt

speckit-converge

Compare codebase implementation against spec, plan, and task artifacts to generate missing tasks.

Community
Advanced
ederfmatosederfmatos

cy-create-techspec

Translate PRD business requirements into technical specifications with ADR documentation.

Community
Advanced