Verified:GitHub

sdd-specify

Generate structured specification documents capturing feature intent and requirements.

Updated Aug 23, 2026

Search Tags:#documentation #workflow automation #product development #feature specification #requirements gathering #intent capture

Ready to run

npx skills add https://github.com/brunoldqueiroz/marvin --skill sdd-specify-brunoldqueiroz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-specify
Source: https://github.com/brunoldqueiroz/marvin/tree/main/.claude/skills/sdd-specify
Command: npx skills add https://github.com/brunoldqueiroz/marvin --skill sdd-specify-brunoldqueiroz

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of capturing the intent and requirements for new features, ensuring clarity before development begins.

Core Features & Use Cases

Intent Capture: Gathers essential details about a feature's purpose and scope.
Structured Specification: Generates a formal document outlining the feature.
Research Integration: Identifies and incorporates necessary research findings.
Use Case: When a product manager has a new idea for an app feature, they can use this Skill to create a detailed specification document that includes user needs, technical considerations, and scope.

Quick Start

Use the sdd-specify skill to create a new feature specification for a user profile page.

Frequently Asked Questions about sdd-specify

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

FAQPage Schema

How do I create a structured feature specification document from initial product ideas?▼

To create a structured feature specification, you need to capture user intent and requirements through targeted questions, identify unknowns, perform research if needed, and generate a formal specification document defining the new functionalities before development begins.

What is the best way to capture intent and requirements for new app functionalities?▼

Capturing intent for new app functionalities requires clarifying the user's goals via specific questions, identifying technical unknowns, and integrating research findings to ensure complete clarity and scope definition before writing the final specification document.

How does specification generation fit into a product development workflow automation process?▼

Specification generation fits into product development workflows by reading existing constitutions, determining spec IDs, and producing structured specification documents that outline user needs and scope, ensuring implementation clarity and reducing development friction.

Do I need an existing constitution document to start gathering requirements for a new feature?▼

Yes, an existing constitution document is required because the feature specification process involves reading the current constitution to determine spec IDs and align the new requirements gathering with established project guidelines before generating the final spec.

Can I integrate research findings directly into my feature specification document?▼

Yes, you can integrate research findings directly into the feature specification because the workflow explicitly identifies unknowns during requirements gathering and performs necessary research to incorporate those findings into the final specification document.

When should I not use automated specification generation for product development?▼

You should avoid automated specification generation for product development when a feature's purpose and scope are already fully defined, or when the workflow lacks an existing constitution to read and determine spec IDs from, making intent capture unnecessary.