feature

Orchestrates a feature prompt through discovery, definition, design, spec, issues, and dev phases to a reviewed PR.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/subvisual/the-a-team --skill feature-subvisual
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature
Source: https://github.com/subvisual/the-a-team/tree/main/.claude/skills/feature
Command: npx skills add https://github.com/subvisual/the-a-team --skill feature-subvisual

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Driving a feature from a raw prompt to a production-ready pull request requires coordinating product discovery, definition, design, specification, issue decomposition, and implementation while preserving human decisions and evidence at each step. This Skill orchestrates that entire A-Team pipeline over a target repository with a manifest as the single source of truth. ## Core Features & Use Cases - Phase orchestration with human gates: Runs discovery, definition, design, spec, issues, dev, and PR phases in order, with human-in-the-loop approval gates at definition, design, and final PR review. - Manifest-driven state management: All state transitions, approvals, retries, and milestones go through a validated CLI with atomic compare-and-swap writes and durable event IDs, making interrupted runs resumable. - Independent dev verification: The dev phase dispatches each issue to an isolated runner where an independent reviewer session approves the diff before it counts as done. - Use Case: Run /feature "Add saved searches" --repo /path/to/target to grill requirements with the human, produce a PRD and design, decompose the spec into Gherkin-acceptance issues, implement them serially in worktrees, and open a reviewed PR. ## Quick Start Ask the AI to run /feature with your feature prompt and target repository path to start the discovery grill and drive the change to a reviewed pull request.

Frequently Asked Questions about feature

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

FAQPage Schema
How do I run a feature from prompt to pull request with an AI agent?▼

Invoke /feature with your prompt and a --repo path to the target git repository. The skill runs discovery, definition, design, spec, issues, and dev phases in order, with human gates at definition, design, and the final PR review.

How do I resume an interrupted feature run?▼

Use /feature resume <slug> --repo <target>. The manifest persists all state with durable event IDs, so a killed session resumes at the same phase or gate, and provisional decisions are presented for review before continuing.

What is the difference between harness and agent orchestration mode?▼

Harness mode runs phase skills on the interactive main thread, while agent mode dispatches role agents like ateam-pm and ateam-designer per agents/TRIAL.md. Both share the same transition CLI, artifacts, gates, and acceptance checks, and the mode is immutable per feature.

Does the dev phase push code or create GitHub issues automatically?▼

No. The dev phase runs with --source local and never touches GitHub; the GitHub issue projection is conditional on an explicit 'github issues: on' config and is skipped for the harness's own repo. The pr phase owns integration and the single PR.

Why does the dev phase reject an issue without acceptance criteria?▼

The independent reviewer session judges each diff only against the issue's checkable Gherkin acceptance criteria. An issue without them returns a needs-detail outcome, which is a decomposition gap to fix in the issues phase, not an implementation error to retry.

What are the prerequisites for running this feature pipeline?▼

You need Node 20+, Git 2+, Python 3, the ateam-runner CLI, the phase skills (ateam-discovery, ateam-definition, ateam-design, ateam-spec, ticket-writer), and an interactive human for gates. Claude Code is required for model execution and gh only for GitHub mode.