run-feature-pipeline

Automating a feature pipeline from backlog to close requires orchestrating requirements, specs, QA design, and execution planning. This Skill coordinates per-story steps, triggers via explicit commands using a slug or code, and outputs context packs, plans, and digest artifacts while gating on blockers.

Yes, you can safely resume feature pipeline automation from the current step. The workflow avoids duplicating work by tracking progress through appended digest blocks and surfaces blockers when encountered, allowing a safe re-run of interrupted implementation and QA tasks.

Managing feature context packs involves building and reusing Project and Feature data to drive consistent prompts. This Skill automatically outputs and manages these context packs to govern the requirements, specs, and execution plans throughout the feature lifecycle.

Yes, feature pipeline orchestration supports parallel execution. It runs execution planning and implementation/QA tasks in parallel where allowed, while gating on blockers, to efficiently progress through feature phases and per-story steps without violating dependencies.

To trigger a feature pipeline run, use an explicit command with a slug or backlog code, such as /run-feature-pipeline F-01.02 nomination-workflow. The system resolves the concrete feature seed and begins orchestrating the end-to-end workflow.