new-app-pipeline
Skill50 starsChanged yesterdayMITView on GitHub
Use when the user wants to take a new app from raw idea to running multi-agent implementation — "/new-app-pipeline", "let's build a new app", "run the app pipeline on this idea". Orchestrates the full sequence - idea → PRD → question refinement → GitHub issues with Execution blocks → execution-plan review → milestone pre-flight → milestone workflow — with a user checkpoint between every stage.
In this repository40 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- app-prdSkill
- cli-dispatchSkill
- codex-validate-fableplan-work-on-issueSkill
- codex-validate-plan-work-on-issueSkill
- create-releaseSkill
- execution-plan-reviewSkill
- expo-app-initializeSkill
- fable-advisorSkill
- fable-dispatchSkill
- fable-new-issue-loopSkill
- fable-new-issueSkill
- fable-orchestrateSkill
- fableplan-loopSkill
- fableplanSkill
- fableplan-work-on-issueSkill
- fable-validate-fableplan-loopSkill
- fable-validate-fableplanSkill
- fable-validate-loopSkill
- fable-validateSkill
- fix-pr-review-loopSkill
- fix-pr-reviewSkill
- github-issue-formatSkill
- issueplanSkill
- milestoneplanSkill
- milestone-workflowSkill
- new-issue-loopSkill
- new-issueSkill
- prd-questionsSkill
- prd-to-issuesSkill
- pr-reviewSkill
- sync-docs-releaseSkill
- sync-docsSkill
- tldrSkill
- validate-fableplan-loopSkill
- validate-issue-loopSkill
- validate-issueSkill
- wansSkill
- work-on-issue-loopSkill
- work-on-issueSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Never skip a checkpoint: Every stage boundary stops for the user.
- Distinctive: line 33
If the artifacts already exist (a PRD in the repo, issues filed), enter at the first stage whose artifact is missing or stale.
- Very specific: line 35
When a milestone already has Execution blocks, run milestoneplan first to check their state before treating stage 5 as finished.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
new-app-pipeline
Each stage produces a durable artifact (PR, issues, workflow run), and those artifacts hold the pipeline state.
Stages
| # | Stage | Skill | Artifact | Checkpoint before next stage |
| 1 | Idea → PRD | app-prd | PRD.md on a PR | User iterates on the draft, in bursts |
| 2 | Resolve questions | prd-questions | Updated PRD, empty Open Questions | User answered every batch |
| 3 | Review and merge the PRD PR | fix-pr-review-loop | PRD on main | Review loop to LGTM on the PRD PR, then explicit user go |
| 4 | Issues + milestones | prd-to-issues | Milestones, complete scoped issues with Execution blocks | User reviews the breakdown table |
| 5 | Execution plan | execution-plan-review | Revised Execution blocks | User settles the final table |
| 6 | Show the plan | milestoneplan | Single per-issue plan table (complexity, dependencies, models, efforts, plan, first review) | User reviews the table (recommended, not required) |
| 7 | Run a milestone | milestone-workflow | Workflow run → PRs → LGTMs | User approves the run plan (mandatory) |
Rules
- Never skip a checkpoint. Every stage boundary stops for the user.
- Stages are re-enterable: the user can jump back ("actually keep Drizzle", "12 should be medium") at any point. Apply each revision to the artifact.
- Stages 6–7 repeat per milestone (v0, then v1, …), chaining workflow invocations where cross-phase dependencies require earlier merges.
- Stage 6 is read-only and skippable; it never edits an issue.
- Tech-stack debates during stage 1–2 (framework, ORM, hosting) are settled in chat and recorded in the PRD's Platforms & Technology table.
- The global CLAUDE.md rules apply throughout, including worktree + PR for every change, attribution footers, and
github-issue-formatbefore filing.
Starting mid-pipeline
If the artifacts already exist (a PRD in the repo, issues filed), enter at the first stage whose artifact is missing or stale; never redo a finished stage. Verify from the repo and issues, without asking the user.
When a milestone already has Execution blocks, run milestoneplan first to check their state before treating stage 5 as finished.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

