Important: This is the v2 of AlignFirst (formerly Vibe Flow). AlignFirst is now distributed as an Agent Skill. If you work with a compatible agent, go ahead. For other agents, you want probably install the v1.
AlignFirst helps produce good plans that enable AI agents to code autonomously. It's distributed as an Agent Skill and works well with any agent powered by a coding model such as:
- Claude Opus 4+ or Claude Sonnet 4+ (Anthropic)
- GPT 5+ (OpenAI)
- Composer 1 (Cursor)
- Gemini 3 Pro (Google)
- Ensure your agent uses a capable coding model.
- Give it this installation prompt.
It will install the AlignFirst skill:
{.claude|.github|.cursor|.codex|.gemini|.agent}/skills/alignfirst/
├── SKILL.md
├── README.md
├── spec-protocol.md
├── plan-protocol.md
├── do-protocol.md
└── description-protocol.md
Then, start using the workflow.
A specification can be written long before the implementation. The agent helps you write it by investigating and initiating a discussion:
/alspec [something to do]The agent will discuss with you, then write a _plans/123/A1-spec.md file.
Note: 123 is the ticket ID. If it can be deduced from the branch name, it will. Otherwise the agent will ask you. A1 means it's the first file of cycle A (files are organized by cycles).
Plans orchestrate what agents or subagents will do:
/alplanThe agent reads the spec and writes a plan _plans/123/A2-plan.md, or a main plan _plans/123/A2-main-plan.md with several sub-plans.
Clear the context, then execute the plan(s):
Execute the plan `_plans/123/A2-main-plan.md`The agent executes the plan and writes .summary.md files.
There is also a lighter prompt for small tasks without specs or plans. Here's how to trigger it:
/al [something to do]The agent will discuss it with you first, then work directly on the codebase. At the end, a _plans/123/A1-AAD.summary.md file will be written.
Agent Skills is an open standard that works out of the box in Claude Code. Editor support is still experimental. Here are the documentations:
Specs, plans, and summaries must be written in well-organized (git-ignored) local files, because:
- The context window is limited, the compression mechanism is opaque, and we want to be able to continue an unfinished task in a fresh session.
- It's a way to keep track of what was agreed upon with the agent and what has been done.
I don't know. If you have a clue, let me know, I'm interested.
The Technical Documentation Authoring skill is independent of AlignFirst but is provided here. It helps you create skills that document your project:
-
Give your agent this installation prompt.
-
Clear the context, then ask it:
Help me bootstrap our project skills. Use technical-documentation-authoring.
It can also work alongside AlignFirst:
/al We need a documentation about [topic]. Use technical-documentation-authoring.- Upgrade from v1: If you have an old
_docs/alignfirst/installation, migrate to the Agent Skills standard - Install AlignFirst Skill
- Install Technical Documentation Authoring Skill
- Update Skills: Update installed AlignFirst and/or Technical Documentation Authoring skills to the latest version
CC0 1.0 Universal.