feature

Enforce a fixed seven-step feature lifecycle from spec to shipped code.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/GarethJB/workflow-plugin --skill feature-garethjb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature
Source: https://github.com/GarethJB/workflow-plugin/tree/main/skills/feature
Command: npx skills add https://github.com/GarethJB/workflow-plugin --skill feature-garethjb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Feature development often suffers from ad-hoc processes where essential steps like spec writing, approvals, and testing are skipped or inconsistently executed. The feature skill enforces a fixed, end-to-end pipeline that ensures every feature passes through a structured lifecycle from spec to shipped code.

Core Features & Use Cases

  • Fixed seven-step workflow: Spec writing → approval → planning → Practice selection → implementation → verification → shipped.
  • Strong governance: locks on spec editing, changelog entries, and traceability to prevent drift and enable rollback or re-entry if needed.
  • Clear entry points and gates: determines where to start based on spec status and ensures no skipping of steps.
  • Collaboration and auditability: keeps a single source of truth for specifications and decisions and records progress in the Changelog.

Quick Start

Start by creating a new spec with the spec-writing workflow, then follow the seven-step pipeline to implement, verify, and ship a feature.

Frequently Asked Questions about feature

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

FAQPage Schema
How do I enforce a strict feature delivery pipeline from spec to shipped code?

To enforce a feature delivery pipeline, you need a fixed workflow that mandates spec creation, approvals, planning, implementation, verification, and changelog discipline. This ensures traceable, auditable software delivery by applying strict gating checks.

What is a fixed end-to-end feature lifecycle in software engineering?

A fixed end-to-end feature lifecycle is a rigid pipeline that turns ideas into shipped software through a seven-step process: spec writing, approval, planning, practice selection, implementation, verification, and shipping.

How do I prevent skipped steps and ad-hoc processes in feature development?

To prevent skipped steps in feature development, apply strong governance with locks on spec editing, traceability, and strict gating checks. This enforces a locked workflow that ensures every feature passes through structured stages.

Can I re-enter or rollback a feature pipeline if the spec drifts?

Yes, you can re-enter or rollback a feature pipeline when spec drift occurs. The pipeline applies locks on spec editing and maintains a single source of truth for decisions, enabling rollback or re-entry if needed.

How do I maintain traceability and auditability for feature implementation?

To maintain traceability and auditability for feature implementation, record progress in a changelog and use frontmatter-driven specs. This keeps a single source of truth for specifications and decisions throughout the delivery pipeline.