create-feature

Coordinate feature delivery from intake through proposal, implementation, review, and pull request preparation.

5|1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/garethrhughes/fragile --skill create-feature-garethrhughes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-feature
Source: https://github.com/garethrhughes/fragile/tree/main/.opencode/skills/create-feature
Command: npx skills add https://github.com/garethrhughes/fragile --skill create-feature-garethrhughes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the uncertainty and inconsistency from non-trivial feature work by guiding you through a complete, project-aligned delivery workflow from intake to pull request.

Core Features & Use Cases

  • Feature Intake and Framing: Captures the feature brief and acceptance criteria before any design or implementation starts.
  • Proposal-Driven Design: Decides whether a change needs a proposal, writes it when needed, and waits for explicit user approval before coding.
  • End-to-End Delivery Control: Coordinates implementation, review, security sign-off, decision logging, and PR preparation while handling iteration loops for feedback or blockers.
  • Use Case: A developer needs to ship a meaningful change that touches architecture or infrastructure and wants a structured process that enforces design review, testing discipline, and release readiness.

Quick Start

Use the create-feature skill to turn my feature idea into a confirmed brief and guide me through the full proposal, implementation, review, and release workflow.

Frequently Asked Questions about create-feature

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

FAQPage Schema
How do I manage feature delivery from intake to pull request for complex architecture changes?

Feature delivery for non-trivial architecture changes requires a structured workflow that captures intake, drives proposal design, enforces TDD implementation, handles code review and security sign-off, and prepares the pull request.

What is a proposal-driven feature development workflow and when do I need it?

A proposal-driven workflow writes a design proposal for non-trivial changes and waits for explicit approval before coding. You need it for product, architecture, or infrastructure changes requiring acceptance gates, TDD, and security sign-off.

How do I implement test-driven development and security checkpoints into my pull request workflow?

Integrating TDD and security into your pull request workflow requires applying test-driven development during implementation, passing an infosec checkpoint, logging architecture decisions, and completing code review before release handoff.

Can I use this structured feature delivery cycle for small bug fixes or minor updates?

This structured feature delivery cycle applies to non-trivial product, architecture, and infrastructure changes requiring proposal-driven workflows. It is not designed for minor updates skipping acceptance gates, ADR logging, or security sign-off.

What's the best way to handle iteration loops and blockers during code review and feature implementation?

Handling iteration loops during feature implementation requires coordinating feedback from code review and security checkpoints, updating TDD coverage, adjusting the proposal if needed, and aligning release handoff once blockers are resolved.