skills.rest
Xantibody
XantibodyCOMMUNITY
Explore all skills by this author →
GitHub

define

Clarify software requirements and produce a requirements document with task breakdown.

1|Updated Dec 12, 2024
Search Tags:#planning#specification#requirements#task breakdown#definition#technical constraints
One-click install
npx skills add https://github.com/Xantibody/dotfiles --skill define-xantibody
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: define
Source: https://github.com/Xantibody/dotfiles/tree/main/configs/claude/skills/define
Command: npx skills add https://github.com/Xantibody/dotfiles --skill define-xantibody

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that all technical requirements and specifications are clearly defined and understood before any implementation begins, preventing costly rework and misunderstandings.

Core Features & Use Cases

  • Requirements Gathering: Elicits detailed functional and non-functional requirements from users.
  • Technical Specification: Analyzes existing code and tools to identify constraints and design policies.
  • Use Case: When a user asks to build a new feature, this skill will ask clarifying questions about its purpose, scope, and technical constraints, producing a formal requirements document and task breakdown.

Quick Start

Use the define skill to clarify the requirements for building a new user authentication module.

Frequently Asked Questions about define

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

FAQPage Schema
How do I clarify software requirements before coding begins?▼

To clarify software requirements before coding, you need to elicit detailed functional and non-functional specifications, analyze codebase context, and resolve ambiguities to produce a formal requirements document and task breakdown.

What is the best way to break down technical specifications for a new feature?▼

Breaking down technical specifications involves analyzing existing code to identify constraints, clarifying the feature's purpose and scope through structured interaction, and generating a comprehensive task breakdown and requirements definition.

How do you gather non-functional requirements and technical constraints for a project?▼

Gathering non-functional requirements and technical constraints requires analyzing the existing codebase and tools to identify design policies, then using structured user interaction to resolve any ambiguities before producing a comprehensive specification.

When do I need a formal requirements definition for software development?▼

You need a formal requirements definition for software development when building a new feature or module, ensuring all technical constraints and specifications are understood to prevent costly rework and misunderstandings during implementation.

Does requirements gathering work without analyzing the existing codebase context?▼

Requirements gathering without analyzing the existing codebase context risks missing critical technical constraints and design policies, making structured codebase investigation necessary to produce an accurate and comprehensive specification document.

Related Skills

Explore More Product & Management Skills→
Davie521Davie521
7

teach-impeccable

Scan a codebase and write design context to .impeccable.md.

Community
Advanced
wiggitywhitneywiggitywhitney

prd-done

Automate branch creation, commits, pull requests, merging, and issue closure via GitHub CLI.

Community
Advanced
EONMUNEONMUN
1

spec_driven_development.plan

Convert clarified specifications into technical plans with architecture, data models, and API contracts.

Official
Advanced
aaronbassettaaronbassett

dapp-sdd:specify

Generate a structured specification document from a dApp README.

Community
Advanced