Skip to content
Skills Library
Management & product · Planning

align

/align

Use when the user needs scope alignment, shared language, or docs clarity before or between gated lanes.

Licence
MIT
Last repository change
29.09.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 29.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when the user needs scope alignment, shared language, or docs clarity before or between gated lanes.

Original author description

Use when the user needs scope alignment, shared language, or docs clarity before or between gated lanes.

How it works

  1. Output
  2. Rules
  3. Procedure
  4. Quality bar
  5. Example
Original SKILL.md headings · 39 lines, 234 words
SKILL.md preview
---
name: align
description: "Use when the user needs scope alignment, shared language, or docs clarity before or between gated lanes."
---

# Align

Use this skill inside Codex when the problem is ambiguity, drift, or mismatched language rather than missing implementation. `align` is a non-gating helper skill.

## Output

Produce:
- current ambiguity or mismatch
- normalized terminology
- scope boundary and exclusions
- acceptance checks or rewritten prompts
- exact next trigger, usually `$maestro` or the lane that owns the next decision

## Rules

- Align language and scope without creating a new release gate.
- Prefer tightening existing artifacts over inventing parallel docs.
- Keep terminology Meta-Architect-native for user-facing surfaces.
- Use `references/shared-language.md` for naming, taxonomy, and docs-clarity patterns.

## Procedure

1. Identify the exact artifact, decision, lane, and owner currently in scope.
2. Separate facts already verified from assumptions, requests, and unresolved choices.
3. Normalize conflicting terms into one product-native vocabulary and record exclusions.
4. Rewrite the smallest useful prompt, acceptance check, or handoff note.
5. Return the next owner and trigger; do not silently advance a gated lane.

## Quality bar

- Every recommendation names its evidence or labels the gap as unknown.
- Scope changes are explicit and reversible.
- The result is actionable by one next owner, not a broad list of suggestions.

## Example

For “the release flow is drifting,” distinguish the package version, Git tag, release workflow, and published artifact before proposing a correction. Route implementation to the owning lane after the terminology and boundary are stable.
Files in this package (3)
  • SKILL.md 2 KB
  • agents/openai.yaml 1 KB
  • references/shared-language.md 1 KB

Versions

RepositoryScoreLicence
This page · justinedevs/meta-architect100MIT
tony/skills100MIT
andriiklymiuk/corgi100MIT
hmmhmmhm/aligns.md100MIT
pandysp/claude-plugins100MIT
hmmhmmhm/aligns.md90MIT
70-10/claude-code-plugins82MIT

Identical content appears in 2 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version a7adc7255c38 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 91ogt-docs-create-task
    Create and manage task documents in the docs/todo/ workflow. Use when creating new tasks, updating task status, or moving tasks between workflow stages. Provides complete task lifecycle management with verification.
  • 87large-project-gated-delivery
    Use when coordinating a large multi-milestone gated project.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.