| name | description | metadata | ||||
|---|---|---|---|---|---|---|
workflow |
Human-readable guide to the AI-assisted implementation workflow using Change Requests, checkpoint commits, and phased execution. |
|
This document describes the end-to-end workflow for implementing changes in this repository using AI agents, Change Requests (CRs), and checkpoint commits.
flowchart TD
A[Create CR] --> B[Iterate CR]
B --> C[/checkpoint-commit/]
C --> D[Implement each phase]
D --> E[Finalize implementation]
E --> F[Push & create PR]
F --> G[Review & merge]
Ask the AI agent to create a CR for the desired change. The CR captures motivation, current state, proposed changes, and a phased implementation plan.
Prompt:
Create a CR for <description of the desired change>
Review the generated CR and refine it until it meets quality standards. This can be zero-shot (accepted on first attempt) but is typically few-shot (a few rounds of feedback).
Prompt (repeat as needed):
<feedback on the CR>
Once the CR is finalized, create a checkpoint commit to preserve it.
Prompt:
/checkpoint-commit
For each phase defined in the CR, execute the following sub-steps in a clean context window:
flowchart TD
A[Clear context window] --> B[Read checkpoints]
B --> C[Implement phase]
C --> D[Checkpoint-commit]
D --> E{More phases?}
E -->|Yes| A
E -->|No| F[Finalize]
Start with a fresh context to avoid confusion from prior conversation.
Action:
/clear
Recover context from previous work by reading checkpoint commits.
Prompt:
/checkpoint-read
Direct the agent to systematically implement the current phase.
Prompt:
Systematically implement phase {phase number} of @path/to/cr.md
Preserve the phase's work with a checkpoint commit.
Prompt:
/checkpoint-commit
Repeat steps 4a–4d for each phase in the CR.
After all phases are complete, run a finalization pass to ensure everything is consistent and complete.
Prompt:
Finalize the implementation of @path/to/cr.md
Push the branch and create a pull request.
Prompt:
git push and create a pr
Review the PR for correctness, completeness, and adherence to project standards.
If the review surfaces issues, fix them and return to step 7.
flowchart TD
A[Review PR] --> B{Issues found?}
B -->|Yes| C[Fix issues]
C --> A
B -->|No| D[Approve]
Squash merge the PR into main. The PR title becomes the commit message and must follow Conventional Commits.
Release Please automatically creates a release PR based on conventional commit messages. Merge the release PR to publish the new version.
flowchart TD
A[Create CR] --> B[Iterate CR]
B --> C[/checkpoint-commit/]
C --> D[/clear/]
D --> E[/checkpoint-read/]
E --> F["Implement phase N"]
F --> G[/checkpoint-commit/]
G --> H{More phases?}
H -->|Yes| D
H -->|No| I[Finalize implementation]
I --> J[Push & create PR]
J --> K[Review]
K --> L{Issues?}
L -->|Yes| M[Fix issues]
M --> K
L -->|No| N[Squash merge]
N --> O[Release Please]