SDLC blueprint

Setup & adoption

A guided flow for consuming repos to adopt Forge SDLC. Includes a questionnaire to determine team configuration, a scaffold script to create directories and files, and a Cursor rule for conversational

Setup & adoption

A guided flow for consuming repos to adopt Forge SDLC. Includes a questionnaire to determine team configuration, a scaffold script to create directories and files, and a Cursor rule for conversational setup.

Adoption steps

  1. Answer the questionnaire — determine team size, roles, product stage, and active disciplines.
  2. Run the scaffold script — creates forge/, ember-logs/, and initial configuration.
  3. Configure Versonas — copy relevant Versonas templates to .cursor/rules/.
  4. Configure Cursor rules — copy daily and planning rules to .cursor/rules/.
  5. Start working — first refinement, first Charge, first Ember Log entry.

Files

File Purpose
Forge setup questionnaire Questions to determine Forge configuration
forge-init.sh Scaffold script — creates workspace directories and seed files
forge.config.template.yaml Configuration template
forge-setup.mdc.template Cursor rule for guided setup
../tasklets/install-tasklets.sh Copy example tasklets + Sampling Versona into .cursor/rules/
Forge `forge.config.yaml` ↔ `.cursor/rules/` alignment Map forge.config.yaml versona.* flags → expected versona-*.mdc files
check-forge-cursor-alignment.sh Script: list missing Versona rules under .cursor/rules/ (needs PyYAML)

Quick start

From the consuming repository root:

./blueprints/sdlc/methodologies/forge/setup/forge-init.sh

This creates the minimal Forge workspace. Then configure using the questionnaire or the Cursor rule.

Canonical source

Edit https://github.com/autowww/blueprints/blob/main/sdlc/methodologies/forge/setup/README.md first; regenerate with docs/build-handbook.py.