# Factory Plan

Produce a phased implementation plan for a Factory work item, then advance it to execute

- Repository: https://github.com/mastra-ai/mastra (29259 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add mastra-ai/mastra --skill factory-plan -g -a claude-code -y`
Codex: `npx skills add mastra-ai/mastra --skill factory-plan -g -a codex -y`
Cursor: `npx skills add mastra-ai/mastra --skill factory-plan -g -a cursor -y`
Gemini CLI: `npx skills add mastra-ai/mastra --skill factory-plan -g -a gemini-cli -y`

## Description

Produce a phased implementation plan for a Factory work item, then advance it to execute

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Factory Plan

Produce a phased, verifiable implementation plan for this Factory work item, then advance it to the `execute` stage with the plan as the handoff.

You are working in a bound Factory session. Complete the full planning pass in one run, then make `factory_transition_work_item` your terminal step, one transition request, repeated only if the governed transition rejects it and only with the rejection reason addressed. Never wait for or solicit human input mid-run; every design decision is yours to resolve.

**Continuity:** if this conversation already contains a triage/understanding pass for this work item, build on it, verify its key claims against the current code rather than re-deriving them. If not (fresh thread), first perform the understanding pass yourself before planning: trace the issue's history, architecture, contributing areas, and root cause as `factory-triage` does. Never plan against an understanding you haven't verified.

**Decision rule:** at every design fork, approach A vs B, scope boundaries, test strategy, migration handling, pick the option the codebase's history and patterns best support, proceed, and **record the decision as an assumption** for the terminal handoff. Reserve open questions for decisions a human genuinely must make (product trade-offs, breaking-change tolerance, priority calls); everything answerable from code, history, or convention is an assumption, not a question.

The rest: https://github.com/mastra-ai/mastra/blob/HEAD/mastracode/factory/factory-skills/factory-plan/SKILL.md