Inputs intake after bootstrap
After a2c init or a2c bootstrap, you often have draft ADRs, architecture notes, and workflow material in a local inputs/ folder. That folder is intake scratch space — not part of the governed repository.
Use the inputs intake prompt to migrate drafts into canonical paths (docs/adr/, docs/architecture/, etc.) following A2C rules, then add inputs/ to .gitignore so Git ignores it permanently.
Prompt asset: pathname:///a2c-assets/prompts/bootstrap/inputs-intake.md.
Workflow
- Run
a2c bootstrap(orinitthenbootstrap). - Place drafts under
inputs/(any subfolders are fine). - Run the inputs intake prompt in your AI IDE (see below).
- Execute batches
batch-intake-00…batch-intake-04sequentially. - Confirm
inputs/is listed in.gitignoreand not tracked.
Invoke the prompt in Cursor (no copy-paste)
In Cursor chat, reference the prompt file with @ so the agent loads the full contract:
Copy delivery (default bootstrap)
Method prompts were copied into this repo:
@prompts/bootstrap/inputs-intake.md
Start batch-intake-00: inventory inputs/ and produce a migration plan.
Submodule or clone (--with-ai-rules)
Method prompts live under the mounted method repo:
@tools/ai-rules/prompts/bootstrap/inputs-intake.md
Start batch-intake-00: inventory inputs/ and produce a migration plan.
Tips
- Type
@and begin typinginputs-intake— Cursor filters matching files in the workspace. - Add a one-line task after the
@reference (batch id, scope, or “inventory only”). - For ADR migration batches, combine with
@prompts/phases/adr-create-update.mdwhen recording a single new ADR. - Stop after each batch; advance to
batch-intake-01, etc., in a new message when ready.
Same pattern works in other @-aware hosts: reference the prompt path, then state the current batch.
Related
- ../cursor-integration.md — Cursor rules and prompt entry points
- ../cli.md —
a2c bootstrapand validation commands - pathname:///a2c-assets/prompts/bootstrap/docs-first-bootstrap.md — docs-only batches after intake