start-feature

Route known software changes to the correct next workflow before implementation.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/0xdeafcafe/skills --skill start-feature-0xdeafcafe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-feature
Source: https://github.com/0xdeafcafe/skills/tree/main/skills/start-feature
Command: npx skills add https://github.com/0xdeafcafe/skills --skill start-feature-0xdeafcafe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly triage a known software change and choose the right workflow before implementation begins. It prevents wasted effort by determining whether a change needs planning, ADR backfill, or can skip scaffolding entirely.

Core Features & Use Cases

  • Work Intake Routing: Identifies whether the request is a new feature, an update to existing code, or a trivial change.
  • ADR and Spec Discovery: Checks the repository for existing architectural decisions or specs relevant to the affected area.
  • Skill Handoff: Routes into the correct follow-on process such as planning a change or backfilling an undocumented feature area.
  • Use Case: When a developer says they want to add a feature, fix a bug, or refactor an existing module, this Skill determines the proper path without drifting into design discussions too early.

Quick Start

Ask the assistant to use start-feature when you already know the code change you want to make and need it routed to the correct next skill.

Frequently Asked Questions about start-feature

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

FAQPage Schema
How do I route a code change to the right workflow before implementation?

To route a code change, you triage the request through concise intake questioning to determine if it needs planning, ADR backfill, or can skip scaffolding entirely. This prevents wasted effort by directing the work to the correct next step.

What is the best way to triage a feature request without drifting into design discussions?

Triage a feature request by identifying the work type and checking for existing ADR or spec coverage in the repository. This routing process explicitly avoids design discussion and hands off directly to planning or backfill skills.

When do I need to backfill an ADR for a refactor or bug fix?

You need to backfill an ADR when repository discovery reveals missing architectural decisions or specifications for the affected module. This routing step ensures undocumented areas are properly specified before implementation begins.

Can I use automated routing for trivial UI tweaks that do not need full feature planning?

Yes, automated routing identifies trivial UI tweaks and skips scaffolding entirely. The intake process determines whether a change requires full planning or can proceed directly to implementation without unnecessary overhead.

Does feature planning routing work for both new features and updates to existing modules?

Feature planning routing works for new features, bug fixes, refactors, and updates to existing modules. It evaluates ADR and specification coverage for each type to determine the correct workflow path before implementation.