Alignfirst

Skill paleo/alignfirst/skills/alignfirst

Companion products for AI-assisted software work.

Install

npx -y skills add paleo/alignfirst --skill alignfirst

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Collaborative problem-solving protocols. Write technical specifications (spec, or alspec), create implementation plans (plan, or alplan), or use Align-and-Do Protocol (AAD). Also generates PR/MR descriptions (aldescription) and code review reports (alreview).

The file declares its own license as CC0 1.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.9 KB, as published. Nobody here has run it

AlignFirst Guide

If you don't already know which protocol to use, read overview.md first.

Protocols

Technical Specification (spec, or alspec): spec-protocol.md
Implementation Plans (plan, or alplan): plan-protocol.md
Align-and-Do Protocol (AAD): aad-protocol.md
Description (aldescription): description-protocol.md
Code Review (alreview): review-protocol.md
Merge (merge, or almerge): merge-protocol.md

TASK_DIR Location

TASK_DIR is the directory where work files related to a task are stored. Usually, we use TASK_DIR = .plans/{TICKET_ID}/ (a sub-directory of the .plans folder). If no ticket ID is known, ask the user for it.

Create TASK_DIR if it doesn't exist
Or, list all existing files (do not truncate)

File Naming Convention

Format: {CYCLE_LETTER}{FILE_NUMBER}-{FILE_TYPE}.md

Common file types:

spec - technical specification
plan - implementation plan
AAD.summary - AAD summary document
description - PR/MR description
review - code review report
merge.summary - merge conflicts resolution summary

Example structure:

.plans/
├── 123/
│   ├── A1-spec.md
│   ├── A2-plan.md
│   └── A3-AAD.summary.md
│   └── B1-spec.md

Shared files: the .plans directory is gitignored, except for files renamed with a .shared.md suffix (e.g. A1-spec.shared.md). We use this suffix to hand work over to another team member, or to collaborate on it.

Notes

TICKET_ID is a unique identifier for the task, often an issue or ticket number.
Cycles are identified by a CYCLE_LETTER (A, B, C...).
The protocol or the user decides whether the next file continues the current cycle or starts a new one.
To determine the next filename in the current cycle: find the highest CYCLE_LETTER, then the highest FILE_NUMBER within it. Bump the number.
For a new cycle: bump CYCLE_LETTER and reset FILE_NUMBER to 1.
Do not bother the user with CYCLE_LETTER or FILE_NUMBER. They are for internal organization. Start CYCLE_LETTER with A if there is no existing cycle. So you just need to ask for a ticket ID if you don't have one.
There is no strict sequence of file types in the workflow. Available file types are also flexible; if you need a new one, just create it.