How do I install the Alignfirst skill?

Run npx skillmds add majiayu000/alignfirst in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Alignfirst skill do?

Choose the appropriate protocol based on the task: It is listed under Productivity on SkillMD.

Is Alignfirst safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Alignfirst?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Alignfirst free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Alignfirst?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Alignfirst by majiayu000 — Agent Skill

Name: Alignfirst
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

File contents

name: alignfirst description: 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). license: CC0 1.0 metadata: author: Paleo version: "2.1.8" repository: https://github.com/paleo/alignfirst

AlignFirst Guide

Protocols

Choose the appropriate protocol based on the task:

Technical Specification (spec, or alspec): Read spec-protocol.md to write a technical specification
Implementation Plans (plan, or alplan): Read plan-protocol.md to create implementation plans from a spec
Align-and-Do Protocol (AAD): Read do-protocol.md for smaller tasks without formal spec/plans
Description (aldescription): Read description-protocol.md to write a description summarizing implemented work

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 existing files

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

Example structure:

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

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 user decides when to start a new one.
In a cycle, determine the next FILE_NUMBER from existing file names. Every new file must have a bumped file number.
Do not bother the user with CYCLE_LETTER or FILE_NUMBER. They are for internal organization. It's up to you to list the files and determine the last CYCLE_LETTER and FILE_NUMBER. Start CYCLE_LETTER with A if there is no existing cycle, and FILE_NUMBER with 1. So you just need to ask for a ticket ID if you don't have one.
When the user requests a new cycle: bump CYCLE_LETTER and reset FILE_NUMBER.
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.

---name: alignfirstdescription: Choose the appropriate protocol based on the task:--- --- name: alignfirst description: 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). license: CC0 1.0 metadata: author: Paleo version: "2.1.8" repository: https://github.com/paleo/alignfirst --- # AlignFirst Guide ## Protocols Choose the appropriate protocol based on the task: - **Technical Specification** (_spec_, or _alspec_): Read [spec-protocol.md](spec-protocol.md) to write a technical specification - **Implementation Plans** (_plan_, or _alplan_): Read [plan-protocol.md](plan-protocol.md) to create implementation plans from a spec - **Align-and-Do Protocol** (_AAD_): Read [do-protocol.md](do-protocol.md) for smaller tasks without formal spec/plans - **Description** (_aldescription_): Read [description-protocol.md](description-protocol.md) to write a description summarizing implemented work ## 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 existing files ## 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 **Example structure:** ```text _plans/ ├── 123/ │ ├── A1-spec.md │ ├── A2-plan.md │ └── A3-AAD.summary.md │ └── B1-spec.md ``` ## 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 user decides when to start a new one. - In a cycle, determine the next **FILE_NUMBER** from existing file names. Every new file must have a bumped file number. - Do not bother the user with CYCLE_LETTER or FILE_NUMBER. They are for internal organization. It's up to you to list the files and determine the last CYCLE_LETTER and FILE_NUMBER. Start CYCLE_LETTER with `A` if there is no existing cycle, and FILE_NUMBER with `1`. So you just need to ask for a **ticket ID** if you don't have one. - When the user requests a new cycle: bump CYCLE_LETTER and reset FILE_NUMBER. - 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.

Frequently asked questions