Handbook
Forge SDLC orchestration
Normative hub for who routes, who orchestrates end-to-end methodology passes, who merges multi-lens output, and who owns specialist judgment (discipline §5), across SDLC phases A–F.
| Document | Purpose |
|---|---|
| Forge SDLC orchestration — roles, phases, merge, trace | Role boundaries, phase-aware contracts, merge/escalation rules, trace outputs, diagrams |
workflows/phases.json |
Machine-readable phase descriptors (companion to the Markdown) |
schema/workflow-phases-bundle.schema.json |
JSON Schema for phases.json |
Cursor rule: ../versona/catalog/workflow/versona-forge-sdlc.mdc.template — install as versona-forge-sdlc.mdc (included in sync --preset recommended).
Supersession: Standards precedence — which controls win — external / org controls override orchestration suggestions.
Related: Forge — connection to the SDLC foundation · Product planning · Versona framework — kinds, interfaces, processes, sessions §6 · ../versona/catalog/routing/versona-all.mdc.template · Versona skill and tasklet matrix §0
Product vs project vs routing (short)
| Versona | Lens | Not this lens |
|---|---|---|
versona-product-management |
What to build and why (strategy, roadmap, OKRs, market fit) | Delivery when/who/how much — that is versona-pm |
versona-pm |
Whether delivery is feasible (constraints, dependencies, RAID, gates) | Roadmap prioritization or vision — versona-product-management |
versona-ba |
Requirements quality, needs, AC, elicitation | Strategy trade-offs — product-management; plan baselines — pm |
versona-all |
Who to invoke across families | Phase orchestration — versona-forge-sdlc; domain merge — versona-family-* |