skills.rest
grimlor
grimlorCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

feature-workflow

Enforce a spec-before-code workflow with gated checkpoints and BDD tests.

2|Updated Mar 5, 2026
Search Tags:#workflow#testing#architecture#specification#coverage#bdd#commit discipline
One-click install
npx skills add https://github.com/grimlor/universal-dev-skills --skill feature-workflow-grimlor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-workflow
Source: https://github.com/grimlor/universal-dev-skills/tree/main/skills/feature-workflow
Command: npx skills add https://github.com/grimlor/universal-dev-skills --skill feature-workflow-grimlor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevents AI coding agents from rushing into implementation by forcing a disciplined, spec-before-code feature lifecycle that reduces rework, scope creep, and undocumented behavior.

Core Features & Use Cases

  • Feature Definition with gated checkpoint: Converts a feature request into a bounded scope and initializes a plan, then waits for user acknowledgment before progressing.
  • Behavioral Spec Gate and architecture review: Ensures a reviewed, complete spec exists and that internal architecture decisions are explicitly approved before any code changes.
  • BDD-driven development with quality baselines: Runs lint/type/audit checks on existing files, validates external API assumptions, writes failing BDD tests from the spec, implements to satisfy those tests, and verifies 100% coverage with an explicit plan closure.
  • Prerequisite workflow spawning: Routes into refactor-workflow when structural prerequisites are required, and resumes the feature workflow after the prerequisite merges.

Quick Start

Use the feature-workflow skill when the user asks for a new feature or enhancement so the agent first defines scope, confirms a reviewed spec, then designs, tests, implements, and verifies coverage before closing the plan.

Frequently Asked Questions about feature-workflow

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

FAQPage Schema
How do I enforce a spec-first feature workflow with AI coding agents?▼

A spec-first feature workflow enforces phased gating with user checkpoints, requiring reviewed behavioral specs and architecture approval before any code changes occur. This prevents AI agents from rushing into implementation and reduces undocumented behavior.

What is BDD-driven feature development and when do I need it?▼

BDD-driven feature development requires writing failing behavioral tests from a reviewed specification before implementing code to pass them. You need this process for new features, enhancements, or behavior-changing updates to ensure minimal rework and maximal traceability.

How to achieve 100% statement and branch coverage verification before closing a feature plan?▼

100% statement and branch coverage verification requires running lint, type, and audit checks, writing failing BDD tests from the spec, and implementing code without test suppression. Plan closure only happens after coverage is explicitly verified.

Does the feature workflow process apply to code refactoring or bug fixes?▼

The feature workflow process does not apply to pure refactoring, bug divergence, or comment, format, and typo-only updates. It specifically targets new features, enhancements, and behavior-changing changes requiring spec-before-code discipline.

Can I route structural refactoring tasks as a prerequisite before resuming feature implementation?▼

You can route structural refactoring tasks by spawning a prerequisite workflow, which handles the structural changes first. The primary feature workflow resumes automatically after the prerequisite refactoring merges.

Why validate external API assumptions before writing BDD tests for a new feature?▼

Validating external API assumptions before writing BDD tests ensures your behavioral specifications are grounded in accurate external premises. This prevents test implementation from failing later due to invalid API integration expectations.

Related Skills

Explore More Software Engineering Skills→
mattphanmmattphanm

refactor

Refactor code safely with baseline tests and incremental validation.

Community
Advanced
atxinskyatxinsky
4

finishing-a-development-branch

Validate tests and execute merge, PR, keep, or discard options for a development branch.

Community
Advanced
fakhriaditiarahmanfakhriaditiarahman
1

test-automator

Automate software testing with Playwright, Selenium, and CI/CD integration.

Community
Advanced
xenotaurxenotaur
1

lrh-implement

Execute software development tasks through a structured planning, implementation, and validation workflow.

Community
Advanced