Handbook

Templates

Copy into docs/ (or your doc root) and customize. Not part of the process itself—shortcuts for new projects.

Project sdlc/ workspace

Canonical files for a mutable sdlc/ folder at repo root (see Initializing the project `sdlc/` workspace and ../scripts/README.md).

Path Use
SDLC — {{PROJECT_NAME}} Render to sdlc/README.md with {{PROJECT_NAME}} replaced (script does this).
Tracking foundation (single spine) Copy into sdlc/ — engineering tracking foundation.
Methodologies (lenses on the tracking foundation) Copy into sdlc/ — methodology lenses.
Tracking challenges (separate from the foundation) Copy into sdlc/ — limits and caveats.

Docs (docs/)

File Use
Roadmap — {project name} Optional milestone/epic table; pair with a WBS or backlog elsewhere.
Test plan — [scope] Optional scope-level test plan (levels, environments, traceability, exit criteria).

Forge SDLC workspace

Seed files for a mutable forge/ workspace and ember-logs/ at repo root. See Setup & adoption for adoption guide.

Path Use
Forge workspace Forge workspace README with directory structure and script references.
forge/forge.config.template.yaml Project Forge configuration (team, Versonas, Assay Gate, paths).
Charge — YYYY-MM-DD Daily Charge seed file.
Ember Log — YYYY-MM-DD Ember Log daily file seed.
Journal — YYYY-MM-DD Day journal seed.
Assay Gate — {Product Spark name} Assay Gate evidence checklist.
Retro Record — — — Retro Record — themes, experiments, evidence pointers, triage toward directives (Forge — ceremonies & events (prescriptive) § “From retro to directives”).
Directive Change Proposal — DCP-- Directive Change Proposal (DCP) — bridge before merging sdlc/ or technical directive updates.
— Project SDLC directive</a></td> <td>Project SDLC directive seed (methodology / process).</td> </tr> <tr> <td><a href="sdlc--templates-forge-technical-directive.template.html"><Title> — Technical directive</a></td> <td>Technical directive seed (implementation standards); pair with ADR when architecture forks.</td> </tr> <tr> <td><a href="sdlc--templates-forge-versona-session.template.html">Versona session — <session-id></a></td> <td>Versona session folder seed (<code>SESSION.md</code> + manifest fields) — see <a href="sdlc--methodologies-forge-versona-versona-framework.html">Versona framework — kinds, interfaces, processes, sessions</a> §7.</td> </tr> <tr> <td><a href="sdlc--templates-forge-discipline-spike-open.template.html">Discipline exploration spike — open checklist</a></td> <td>Exploration spike open checklist (hypothesis, anchors, no-roadmap branch) — <a href="sdlc--methodologies-forge-versona-discipline-spike.html">Discipline exploration spike — lifecycle and anchors</a>.</td> </tr> <tr> <td><a href="sdlc--templates-forge-discipline-spike-close.template.html">Discipline exploration spike — close record</a></td> <td>Exploration spike close record (<code>outputs/SPIKE-CLOSE.md</code>), Ember Log + git prompts.</td> </tr> <tr> <td><a href="forge/session.manifest.yaml.template"><strong>forge/session.manifest.yaml.template</strong></a></td> <td>Optional YAML twin of session manifest.</td> </tr> <tr> <td><a href="sdlc--templates-forge-versona-process.template.html">Process: <process-id></a></td> <td>Repeatable multi-step Versona / human process doc (diagram-as-code placeholders).</td> </tr> <tr> <td><strong>forge/cursor-rules/</strong></td> <td>Ready-to-use Cursor rules: <code>forge-daily.mdc</code>, <code>forge-planning.mdc</code>, <code>forge-setup.mdc</code>, <code>forge-versona.mdc</code>, <code>forge-product-manager.mdc</code>. Optional Layer-0 baseline: copy <code>../methodologies/forge/versona/versona-generic.mdc.template</code> from blueprints (see <code>versona/catalog/ANCESTRY.md</code>, <code>versona/catalog/TEMPLATE-INDEX.md</code>).</td> </tr> <tr> <td><strong>forge/cursor-skills/</strong></td> <td>Optional Cursor <strong>Skills</strong> to copy into <code>.cursor/skills/</code> (e.g. <code>run-product-versona-session</code>, <code>run-engineering-ai-code-review</code>).</td> </tr> <tr> <td><strong>—</strong></td> <td>Cursor rules: <a href="../methodologies/forge/setup/sync-forge-cursor-rules.sh"><code>../methodologies/forge/setup/sync-forge-cursor-rules.sh</code></a> (<code>sync</code> / <code>diff</code> / <code>status</code> / <code>check</code>) — quick ref <a href="sdlc--methodologies-forge-setup-cursor-rules-quickstart.html">Cursor rules — quickstart (Forge + Versonas)</a></td> </tr> </tbody> </table></div> <h2 id="spec-driven-sdd--ceremony--process-io">Spec-driven (SDD) — ceremony & process I/O</h2> <div class="forge-table-wrap mt-2 mb-3"><table class="table table-sm table-striped mb-0"> <thead> <tr> <th>Path</th> <th>Use</th> </tr> </thead> <tbody> <tr> <td><a href="sdlc--templates-sdd.html">SDD templates (Spec-driven development)</a></td> <td>Blank specs for <strong>inputs/outputs/preconditions</strong> (agents, product, engineering).</td> </tr> <tr> <td><a href="sdlc--templates-sdd-ceremony-intent.template.html">SDD: REPLACE — ceremony name</a></td> <td>Map <strong>C1–C6</strong> or team rituals to SDD tables.</td> </tr> <tr> <td><a href="sdlc--templates-sdd-process-slot.template.html">SDD: REPLACE — process slot</a></td> <td>Gates, release slices, toolchain steps.</td> </tr> </tbody> </table></div> <p>Normative schema and worked examples: <a href="sdlc--methodologies-spec-driven.html">Spec-driven development — SDD I/O package</a> · handbook HTML: generated under <code>blueprints/website/</code> by <code>generator/build-handbook.py</code> (e.g. <code>sdlc--methodologies-spec-driven-sdd-io-schema.html</code>).</p> </div> <div class="col-lg-4 col-xl-3 order-1 order-lg-2"> <nav class="forge-toc" aria-label="On this page"> <p class="toc-title mb-2">On this page</p> <a class="nav-link" href="#project-sdlc-workspace">Project sdlc/ workspace</a> <a class="nav-link" href="#docs-docs">Docs (docs/)</a> <a class="nav-link" href="#forge-sdlc-workspace">Forge SDLC workspace</a> <a class="nav-link" href="#spec-driven-sdd--ceremony--process-io">Spec-driven (SDD) — ceremony &amp; process I/O</a> </nav> </div> </div> <nav class="d-flex flex-wrap justify-content-between gap-2 mt-4 pt-3" style="border-top:1px solid var(--forge-border)" aria-label="Chapter navigation"><a href="sdlc--team-rollout.html" class="btn btn-cyan-outline btn-sm">← Team rollout patterns</a><a href="sdlc--templates-roadmap.template.html" class="btn btn-forge-outline btn-sm">Roadmap — {project name} →</a></nav> <footer class="mt-5 pt-4 small" style="border-top:1px solid var(--forge-border);color:var(--forge-text-3)"><p class="mb-1">Last updated: <strong>2026-04-10</strong>.</p><p class="mb-0" style="font-size:.75rem;color:var(--forge-text-4)"></p></footer> </div> </main> </div> </div> <script src="https://cdn.jsdelivr.net/npm/bootstrap@5.3.3/dist/js/bootstrap.bundle.min.js" crossorigin="anonymous"></script> <script src="assets/forge-theme.js"></script> <script src="assets/handbook-portal-nav.js" data-root="."></script> </body> </html>