Skip to main content

Reusing A2C

A2C is designed as a reusable workflow product across future repositories.

Adoption steps​

Brownfield (existing repo): run a2c migrate and follow legacy-adoption.md before or after bootstrap (ADR-0018).

Greenfield / copy workflow:

  1. Copy or reference the workflow structure from a2c-workflow
  2. Bring relevant rules, templates, and prompts (or mount as submodule)
  3. Select an optional stack profile — a2c bootstrap --profile <id> (for example python or publishable python-pypi) or set workflows.default_profile later; see ADR-0016 and ADR-0017
  4. Adapt project identifiers, namespaces, and local AGENTS.md
  5. Create ADR-0000 — adr(workflow): adopt A2C workflow vX.Y.Z
  6. Install shared pre-commit — .pre-commit-config.yaml with mandatory a2c-pre-commit-hooks + standard hooks (including gitlint); a2c bootstrap creates .venv/, installs pre-commit, and registers git hooks when Python and git are available (pre-commit-policy.md, a2c-pre-commit-hooks.md)
  7. Add CHANGELOG.md — root-level file per changelog-policy.md; bootstrap from templates/changelog/CHANGELOG-template.md
  8. Add docs/web-source-mapping.md — external URL registry for [web:NNN] tags (ADR-0011); scaffolded by a2c bootstrap
  9. Regenerate the commit plan for your project's architecture
  10. Execute phases in bounded batches

What to copy vs reference​

ApproachWhen
CopyStandalone project, offline use, heavy customization
Submodule / mountShared policy updates, team alignment with upstream A2C

Local exceptions belong in the project's root AGENTS.md and local overlay rules — not silent edits to shared A2C files.

Stack profiles​

Profiles adapt structure defaults without changing A2C principles. See pathname:///a2c-assets/profiles/README.md.

Example: pathname:///a2c-assets/profiles/python/ for Python packages; pathname:///a2c-assets/profiles/cpp-cmake-conan/ for C++ / CMake / Conan projects.

Docs-portal linkage​

Project-specific A2C artifacts remain docs-as-code in the project repo. The docs-portal provides discovery and cross-project navigation once workflows are registered.

Dogfooding and feedback​

Validate A2C on real projects. Feed lessons back through explicit docs, rules, templates, and ADR updates to a2c-workflow — not ad hoc drift in consumers.