feature-flow

Orchestrates YouTrack ticket intake through spec-driven planning, testing, and PR delivery.

Updated Jul 28, 2026
One-click install
npx skills add https://github.com/CybernetKZ/sdd-kit --skill feature-flow-cybernetkz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-flow
Source: https://github.com/CybernetKZ/sdd-kit/tree/main/templates/_migrated/skills/feature-flow
Command: npx skills add https://github.com/CybernetKZ/sdd-kit --skill feature-flow-cybernetkz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It turns loosely written YouTrack feature and bugfix tickets into merged pull requests through a disciplined spec-driven pipeline, preventing unverified assumptions, missing tests, and unreviewed plans from reaching production. ## Core Features & Use Cases - Ticket intake interrogation: Cross-checks every ticket claim against code, repo specs, and the cross-service contract store, posting contradictions and questions in Russian before any code is written. - Tiered planning pipeline: Picks light, standard, or deep tiers that scale planning depth (OpenSpec change proposals, plan grilling, architecture research) while keeping quality gates fixed. - Test-first implementation: Enforces one test per spec Scenario written by a dedicated test-author agent before the executor agent implements, with reviewer agents checking the diff before PR. - Use Case: A developer receives ticket WEB-1234 asking for a new endpoint; the skill walks them from intake questions through an OpenSpec change, RED tests, implementation on a feature branch, review, and a PR with a Russian QA handoff comment. ## Quick Start Start work on YouTrack ticket WEB-1234 by interrogating the ticket, planning an OpenSpec change, and driving it through tests, implementation, review, and PR.

Frequently Asked Questions about feature-flow

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

FAQPage Schema
How do I start work on a YouTrack ticket with spec-driven development?▼

Read the ticket via the YouTrack MCP, cross-check every claim against the code, repo specs in openspec/specs, and the contract store, then write findings to openspec/changes/<id>/intake.md. Post contradictions and questions in Russian to the ticket author before planning.

What are the light, standard, and deep tiers in this workflow?▼

Tiers scale preparation depth while quality gates stay fixed. Light covers minimal changes with one regression test, standard adds planner and plan-griller agents, and deep adds architecture research in design.md plus a mandatory agent-run grill.

How does test-first development work with OpenSpec Scenarios?▼

The test-author agent writes exactly one test per spec Scenario with a tracer comment before implementation begins, and tests must be RED first. The executor agent implements until tests pass but never edits tests itself.

When should a change be planned as an epic instead of a single PR?▼

A change becomes an epic when it cannot fit a 2-day branch, decided at tier selection time. The epic stays one OpenSpec change split into multiple YouTrack tasks, each producing its own PR, with tests written once upfront.

What happens when a test unexpectedly passes before implementation?▼

An unexpectedly green test is treated as a finding that the behavior may already exist, not something to force red. The team investigates the existing behavior rather than modifying the test to fail.

How are cross-service contract changes handled in this workflow?▼

Contract edits are a separate change and PR in the cybernet-specs store, referenced from the main change's tasks.md. Fixed contracts require an expand/contract migration plan, and the change is not archived while the store PR is open.