spec

Guides users through collaborative specification of software features and fixes via structured, multi-turn dialogue.

Updated Mar 9, 2026

Search Tags:#design #collaboration #software development #specification #technical design #feature planning

Ready to run

npx skills add https://github.com/justinpbarnett/claude --skill spec-justinpbarnett

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/justinpbarnett/claude/tree/main/skills/spec
Command: npx skills add https://github.com/justinpbarnett/claude --skill spec-justinpbarnett

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill acts as a collaborative design partner, guiding users through the process of defining requirements, exploring technical options, and making architectural decisions before implementation begins.

Core Features & Use Cases

Structured Design Process: Guides users through intake, research, exploration, drafting, and review phases.
Collaborative Decision Making: Facilitates multi-turn conversations to resolve technical choices and scope boundaries.
Use Case: When starting a new feature like "user authentication," this Skill will help you decide on the auth strategy (JWT vs. sessions), token storage, and endpoint design through a series of questions and presented options.

Quick Start

Use the spec skill to start designing a new feature for user authentication.

Frequently Asked Questions about spec

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

FAQPage Schema

How do I design and spec complex software features collaboratively before implementation?▼

To design and spec software features collaboratively, you can use a structured conversational process that guides you through intake, research, exploration, drafting, and review phases to produce a detailed implementation plan.

What is the best way to plan technical specifications for a bug fix or refactor?▼

Planning technical specifications for bug fixes or refactors involves a multi-turn conversation that leverages codebase context to define requirements, explore technical options, and resolve architectural decisions before drafting the final spec.

How do I decide on an architectural strategy like JWT vs sessions during feature planning?▼

During feature planning, you can resolve architectural strategy decisions through collaborative decision-making, where a structured dialogue presents technical options and asks targeted questions to help you define scope and choose the best approach.

Can I use this specification process for performance optimization and maintenance chores?▼

Yes, you can use this specification process for performance optimization and maintenance chores, as it supports various software development task types by guiding users through research and decision-making to produce detailed implementation plans.

Do I need to provide codebase context for technical design and specification drafting?▼

Providing codebase context is expected for technical design and specification drafting, as the process leverages user input alongside codebase context to accurately define requirements and produce detailed implementation plans.

What are the limitations of using a multi-turn conversational process for software specification?▼

The multi-turn conversational process for software specification requires active user participation through each phase, meaning it functions as a collaborative design partner rather than an automated, single-prompt specification generator.