feature-factory

Orchestrates a multi-agent pipeline from Linear ticket to merged PR with human checkpoints.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/OgenticAI/ogentic-shield --skill feature-factory-ogenticai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-factory
Source: https://github.com/OgenticAI/ogentic-shield/tree/main/.claude/skills/feature-factory
Command: npx skills add https://github.com/OgenticAI/ogentic-shield --skill feature-factory-ogenticai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating a feature from a ticket to a merged pull request requires many specialized steps — research, story writing, specs, design, multi-stack builds, tests, reviews, and release — and doing this by hand across agents is error-prone and untracked. This Skill runs that entire chain as one orchestrated workflow grounded in Linear. ## Core Features & Use Cases - End-to-end pipeline orchestration: Coordinates twenty specialized agents (researcher, story-writer, spec-writer, builders, reviewers, release-manager) from a Linear ticket to a merged PR. - Human checkpoints and headless mode: Pauses at three approval gates by default, or runs fully autonomously with programmatic gates when FACTORY_HEADLESS=true, escalating failures via needs-human-review labels. - Linear state synchronization: Every agent posts [factory:<agent>] comments, manages labels, and transitions ticket states so Linear remains the source of truth. - Use Case: Say "Build OGE-123 through the factory" and the orchestrator researches the ticket, drafts the story and spec, fans out backend builders in parallel, runs the reviewer panel, opens the PR, and hands off to release — pausing for your approval at each checkpoint. ## Quick Start Ask the assistant to run OGE-123 through the factory to start the full pipeline from that Linear ticket.

Frequently Asked Questions about feature-factory

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

FAQPage Schema
How do I run a Linear ticket through an automated feature pipeline?▼

Invoke the factory with a ticket ID, for example "Build OGE-123 through the factory". The orchestrator reads the ticket, runs research, story, and spec agents, then builds, tests, reviews, and opens a PR, pausing at three approval checkpoints.

How do I run an agent pipeline without human approval checkpoints?▼

Set the environment variable FACTORY_HEADLESS=true before the run. The three human checkpoints are replaced by programmatic gates such as label checks, lint and typecheck gates, and CI-green auto-merge, with failures escalated via a needs-human-review label.

Can the factory handle work that spans multiple repositories?▼

Yes. When the spec lists changes across more than one repo, the ticket gets a cross-repo label and a cross-repo-coordinator creates one sub-issue per repo. Each sub-issue runs its own factory pass, and the parent ticket stays open until all are validator-clean.

What happens when a reviewer finds a critical issue in the pipeline?▼

The finding is routed back to the specific builder named in the finding's file and line, with a blocking label such as validator-blocked or security-blocked. After the fix, the full reviewer panel re-runs, escalating after two consecutive all-Critical rounds.

When should I not use the feature factory workflow?▼

Skip it for one-off bugfixes (use an incident-responder flow), refactors with no user-visible behavior (use a lighter chain), and docs-only PRs. The factory also never runs without a Linear ticket as its source of truth.