Phased execution

A2C work proceeds in explicit phases. Do not jump ahead. Keep steps small and reviewable.

Phase model

Phase	Focus	Typical outputs
1 — Skeleton	Repository anatomy	README, folder tree, minimal metadata
2 — Core docs	Governing documentation	ADR structure, rules, templates, portal note
3 — Execution assets	AI-ready artifacts	Prompt pack, profile example, expanded docs
4 — Tooling	Optional helpers	Small scripts only when clearly justified

Phases are guidance, not a waterfall. Within each phase, work still lands as small commits.

Bootstrap phases for a2c-workflow

This repository was bootstrapped using pathname:///a2c-assets/plans/bootstrap-a2c-workflow.md.

Phase rules for agents

1. Complete the current phase batch before starting the next
2. Propose the file list when uncertain — do not invent speculative structure
3. Prefer Markdown artifacts before code or utilities
4. Stop after the planned batch; wait for review
5. Update the commit plan when scope changes

Mapping phases to commit types

Activity	Typical commit type
Repo skeleton, hooks, CI	chore:
Workflow documentation	docs:
New rules or templates	docs: or feat:
Architectural decision	adr(<category>):
Release version bump	chore(release):

Related

• commit-planning.md
• pathname:///a2c-assets/rules/07-no-big-bang.md