AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified CC0-1.0 Self-run

Alignfirst

skill-paleo-alignfirst-alignfirst · by paleo

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).

↗ Repository
— No reviews yet
0 installs
0 views
— view→install

Install

$ agentstack add skill-paleo-alignfirst-alignfirst

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-paleo-alignfirst-alignfirst)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Alignfirst? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

AlignFirst Guide

If you don't already know which protocol to use, read [overview.md](references/overview.md) first.

Protocols

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

TASK_DIR Location

TASKDIR is the directory where work files related to a task are stored. Usually, we use TASKDIR = .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

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 CYCLELETTER, then the highest FILENUMBER within it. Bump the number.
  • For a new cycle: bump CYCLELETTER and reset FILENUMBER to 1.
  • Do not bother the user with CYCLELETTER or FILENUMBER. 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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills