skills.rest
highflame-ai
highflame-aiOFFICIAL
Explore all skills by this author →
Website𝕏@javelinaiGitHub

feature-prep

Validate feature workflows by enforcing spec registry updates and test placement.

4|Updated Jul 20, 2026
Search Tags:#workflow#testing#architecture#spec-driven#regression#sdlc
One-click install
npx skills add https://github.com/highflame-ai/ai-factory --skill feature-prep
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-prep
Source: https://github.com/highflame-ai/ai-factory/tree/main/skills/feature-prep
Command: npx skills add https://github.com/highflame-ai/ai-factory --skill feature-prep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents architectural drift and test suite bloat by enforcing a mandatory, spec-driven gate before implementation begins for any non-trivial feature.

Core Features & Use Cases

  • Spec Registry Gate: Ensures new platform capabilities or invariants are documented in the spec registry before code is written.
  • Test Placement Logic: Determines whether tests belong in the high-signal org regression suite or the local repository based on service boundaries and user impact.
  • Use Case: When starting a cross-service feature, use this skill to verify if you need to update the architecture registry and where to place your end-to-end tests to maintain system health.

Quick Start

Invoke the feature-prep skill to evaluate the requirements and test strategy for your current feature development task.

Frequently Asked Questions about feature-prep

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

FAQPage Schema
How do I prevent architectural drift when starting cross-service feature development?▼

To prevent architectural drift during cross-service feature development, enforce a mandatory spec-driven gate that validates feature specs and requires architecture registry updates before implementation begins.

How do I determine optimal test placement for end-to-end tests across service boundaries?▼

Optimal test placement for features crossing service boundaries is determined by evaluating user impact and service boundaries to route high-signal tests to the org regression suite rather than local repositories.

What is a spec registry gate and when do I need it for platform capabilities?▼

A spec registry gate is a pre-implementation validation step ensuring new platform capabilities or invariants are documented in the spec registry, needed for non-trivial multi-file features crossing service boundaries.

Do I need to configure a regression repo before validating feature development workflows?▼

Yes, validating feature development workflows requires configuring the regression repo and spec registry beforehand to provide deterministic guidance on spec-first development and regression suite maintenance.

Why does test suite bloat occur and how can spec-driven development reduce it?▼

Test suite bloat occurs when tests are misplaced in local repositories instead of high-signal regression suites; spec-driven development reduces it by enforcing optimal test placement based on service boundaries.

Related Skills

Explore More Software Engineering Skills→
wcyganwcygan
193

lazygit-config

Configure lazygit TUI with delta integration via YAML config files.

Community
Intermediate
inbrainfuninbrainfun
174

testing

Validate skill conformance and run daily health checks across the repository.

Community
Advanced
mohitmishra786mohitmishra786

test

Generate unit, integration, and end-to-end tests with Pytest, Jest, Playwright, and k6.

Community
Advanced
HulupeepHulupeep
24

specflow

Convert plain-language requirements into enforceable YAML contracts for automated rule checks and release gates.

Community
Advanced