wf-docker-feature-framing-method

Decompose ambiguous feature requests into bounded story slices with acceptance criteria.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/belluga/delphi-ai --skill wf-docker-feature-framing-method
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wf-docker-feature-framing-method
Source: https://github.com/belluga/delphi-ai/tree/main/skills/wf-docker-feature-framing-method
Command: npx skills add https://github.com/belluga/delphi-ai --skill wf-docker-feature-framing-method

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose ambiguous feature requests into bounded, story-sized execution slices to guide deterministic TODOs.

Core Features & Use Cases

  • Bounded framing pass: creates a clearly scoped set of story slices for ambiguous work.
  • Feature brief generation: produces lightweight briefs when direct-to-TODO would be premature.
  • Tactical handoff: outputs the current story slice ready to enter the TODO queue, with rationale.

Quick Start

Provide a bounded framing pass for the given request and generate the current story slice ready for tactical TODO.

Frequently Asked Questions about wf-docker-feature-framing-method

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

FAQPage Schema
How do I decompose ambiguous feature requests into bounded story slices?

Decompose ambiguous feature requests by applying a bounded framing pass that breaks down medium to large work into story-sized execution slices. This process delivers the current story slice ready for tactical TODO queues, complete with acceptance criteria and ownership.

What is feature framing in software development and product planning?

Feature framing is a planning technique that scopes unbounded, feature-shaped requests into deterministic execution slices. It decides whether work proceeds directly to a TODO queue or requires a lightweight feature brief for further clarification.

When do I need a feature brief instead of a direct-to-TODO handoff?

You need a feature brief when direct-to-TODO execution would be premature for ambiguous requests. The framing pass evaluates the request boundaries and generates a lightweight brief if the story slice lacks sufficient clarity for deterministic execution.

What's the best way to turn vague product requests into deterministic execution TODOs?

The best way to turn vague requests into deterministic execution TODOs is generating a tactical handoff. This outputs a clearly scoped current story slice with rationale, acceptance criteria, and ownership to guide immediate development.

Does feature framing work for medium to large scale software development requests?

Feature framing works specifically for medium to large scale software development and product planning requests. It is designed to handle feature-shaped work that is too complex for immediate execution but needs bounded story slices.