dev-define

Define feature requirements and architecture from project backlog and plans.

Updated Jan 1, 2026

Search Tags:#planning #architecture #requirements #build #backlog #feature #define

Ready to run

npx skills add https://github.com/AirMile/claude-config --skill dev-define

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-define
Source: https://github.com/AirMile/claude-config/tree/main/skills/dev-define
Command: npx skills add https://github.com/AirMile/claude-config --skill dev-define

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Feature definition and architectural planning are often deferred until late in the project lifecycle, causing scope drift and costly rework. This Skill provides a structured approach to capture feature context, align backlog items, and set architectural constraints before /dev-plan and /dev-build.

Core Features & Use Cases

Gather backlog context, project concepts, and thinking notes to seed a feature definition.
Synthesize decisions into backlog items, project context, and a defined scope for build planning.
Produce a traceable artifact set (backlog, feature.json, and context) that supports planning, review, and execution in early project stages.

Quick Start

Run /dev-define [feature-name] to begin capturing backlog data and architecture decisions for a new feature.

Frequently Asked Questions about dev-define

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

FAQPage Schema

How do I define feature requirements and architecture before starting a build?▼

Feature definition requires gathering backlog context, project concepts, and thinking notes to seed scope and architectural constraints. This prevents scope drift by producing traceable artifacts like backlog items and feature.json for build planning.

What is the best way to extract backlog items for a new software feature?▼

Extracting backlog items involves gathering project context, existing plans, and thinking notes to synthesize decisions. This structured gathering process ensures traceable decisions and ready-to-build documentation for subsequent build phases.

How do I prevent scope drift during early project lifecycle architecture planning?▼

Preventing scope drift requires setting architectural constraints and capturing feature context before build execution. Synthesizing decisions into a defined scope and backlog generates traceable artifacts that anchor subsequent development phases.

Can I use structured feature definition to prepare documentation for build planning?▼

Yes, structured feature definition produces a traceable artifact set including backlog items, feature.json, and project context. These ready-to-build documents directly support planning, review, and execution stages.

When do I need to generate traceable decisions for software architecture planning?▼

Traceable decisions are needed when feature definition and architectural planning occur early in the project lifecycle. Generating a defined scope and backlog before build execution prevents costly rework and aligns development efforts.