Workflows — phase map

Foundry workflows are organised by delivery phase. Pick the phase you're in and follow the standard flow it documents. The end-to-end shape:

1 — Analysis    →   2 — Planning   →   3 — Solutioning   →   4 — Implementation
   (Analyst)         (PM, UX)            (Architect, PM)      (Dev + skills)
   brief +           PRD +               architecture spine    sprint board +
   research          UX spines           + epics & stamps      story/review cycle

Plus the off-cycle paths:

• 5 — Scaffold — one-shot generation of new repos / microservices / SDKs. Bypasses the rest of the lifecycle.
• Quick flow — e11-spec-flow + e11-dev-flow for small work, with a oneshot mode inside.
• Unattended — e11-dev-auto runs a whole iteration with no human, HALTing done or blocked.

Phases

Phase	Workflows	Owner(s)	Page
1 — Analysis	brief (3 intents), PRFAQ, market / domain / technical research	Analyst, Tech Writer	1-analysis.md
2 — Planning	PRD (3 intents), dual-spine UX	PM, UX Designer	2-planning.md
3 — Solutioning	architecture spine, epics & stories, readiness gate	Architect, PM	3-solutioning.md
4 — Implementation	sprint ×2, story ×2, dev-story, code review, checkpoint, QA, retro, correct-course, dev-flow, dev-auto	Dev + direct skills	4-implementation.md
5 — Scaffold	bootstrap wizard + 6 scaffolds	Bootstrapper	5-scaffold.md

Deep pages

Page	Skill(s)	One-liner
Quick flow	e11-spec-flow + e11-dev-flow	The spec kernel and the quick engine, in depth
Unattended runs	e11-dev-auto	Zero-interaction pipeline, HALT protocol, result.json
Checkpoint preview	e11-checkpoint-preview	Guided human review of any change
Discovery	e11-discovery	Facilitated ideation, three stances, 70+ techniques
Multi-perspective	e11-multi-perspective	Roster roundtable on any artifact
Forge idea	e11-forge-idea	Socratic pressure-test before you invest
PRFAQ	e11-prfaq	Working-backwards press release + FAQs

Shared workflows (anytime, not phase-bound)

Available from any agent, any phase:

Code	Skill	Purpose
[BH]	e11-help	Get unstuck — suggests next steps from installed state
[QK]	e11-knowledge	Pull an alloy doc directly (sdk:<name>, pattern:<name>, …)
[RF]	e11-refine	Push the model to reconsider and improve a recent output (72-method catalog)
[MP]	e11-multi-perspective	Roster roundtable — see the deep page above
[FI]	e11-forge-idea	Pressure-test an idea — see the deep page above
[CF]	e11-customize	Author TOML overrides conversationally (Customization)
[SD]	e11-shard-doc	Split a large document (>500 lines) into per-section files
[ID]	e11-index-docs	Build a lightweight index of a docs directory
[AR]	e11-review-adversarial-general	Critically review any artifact
[ECH]	e11-review-edge-case-hunter	Walk every branching path for unhandled boundaries
[VG]	e11-review-verification-gap	Find changed behavior no verification would catch
[RC]	e11-review-reachability	Find what would not work once deployed, and whether each gap is owned
[AA]	e11-review-alloy-auditor	E11 convention + citation-honesty audit on any diff
[EP] / [ES]	e11-editorial-review-prose / -structure	Copy-edit / structural edit passes
[SF] / [DF]	e11-spec-flow / e11-dev-flow	The quick pair — see Quick flow
[DP]	e11-document-project	Brownfield analysis → project documentation
[GPC]	e11-generate-project-context	Lean LLM-optimised project-context.md

Source

Workflow folders:

• 1-analysis/ · 2-plan-workflows/ · 3-solutioning/ · 4-implementation/ · 5-scaffold/
• Anytime skills (e11-knowledge, e11-master, …) under src/foundry/tasks/
• Command catalog: src/foundry/module-help.csv