early-feature-factory

Coordinate end-to-end feature delivery with scoped approvals and orchestration.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ForrestGrump/agent-factory-scaffold --skill early-feature-factory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: early-feature-factory
Source: https://github.com/ForrestGrump/agent-factory-scaffold/tree/main/.agents/skills/early-feature-factory
Command: npx skills add https://github.com/ForrestGrump/agent-factory-scaffold --skill early-feature-factory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In evolving codebases, teams often struggle to align architecture, governance, and workflow as features emerge. This skill provides a repeatable, end-to-end process that guides from initial idea through testing and harness evolution, ensuring architectural stewardship and timely approvals.

Core Features & Use Cases

  • Orchestrates grill-me sessions to define scope, non-goals, acceptance criteria, risks, and initial implementation direction.
  • Assigns architecture stewardship to ensure alignment with existing conventions and to identify missing standards.
  • Facilitates drafting and approval of user stories (02_story) and specifications (03_spec), and coordinates handoffs to implementation.
  • Coordinates unified implementation and validation, including tests and harness updates, for greenfield and young-code repositories.
  • Generates durable run artifacts under .agent-runs and updates project-wide conventions when needed.

Quick Start

Create a new feature run under .agent-runs/<feature-id> and guide the team through the grill-me, story/spec drafting, implementation, and harness evolution steps.

Frequently Asked Questions about early-feature-factory

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

FAQPage Schema
How do I coordinate feature delivery and architecture governance in an evolving codebase?

Feature delivery in an evolving codebase requires a deterministic workflow that guides scope, approvals, and orchestration. This skill assigns architecture stewardship and coordinates handoffs from planning to implementation, ensuring alignment with existing conventions and timely approvals.

What is the best way to write user stories and specifications for early-stage projects?

Writing user stories and specifications for early-stage projects is facilitated through dedicated drafting and approval phases. The workflow assigns specific roles like story-writer and spec-writer to generate structured artifacts under .agent-runs, ensuring clear acceptance criteria before implementation.

How do I define feature scope and non-goals for young-code repositories?

Defining feature scope for young-code repositories is handled through orchestrated grill-me sessions. These sessions identify non-goals, acceptance criteria, risks, and initial implementation direction, providing a repeatable process that aligns emerging architecture with governance standards.

Can I use this workflow to manage testing and harness evolution alongside implementation?

Testing and harness evolution are directly managed within this workflow. It coordinates unified implementation and validation, updating tests and harness configurations as needed, and generates durable run artifacts while updating project-wide conventions in AGENTS.md.

Does this feature orchestration approach work for greenfield projects where conventions are still forming?

Feature orchestration works effectively for greenfield and young-code repositories where conventions are still forming. It enforces a deterministic workflow with project-architect and orchestrator roles to establish missing standards and guide end-to-end feature delivery.