How do I install the Adjust skill?

Run npx skillmds@latest add telum-ai/adjust 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.

Is Adjust safe to use?

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

Which AI agents work with Adjust?

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 Adjust free to use?

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

Who published Adjust?

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

Adjust by telum-ai — Agent Skill

Name: Adjust
Rating: 4.2 (5 reviews)
Author: telum-ai

File contents

adjust

Canonical adjustment engine for intentional changes to validated or shipped work. Defects with no promise change route to /harden.

Cheap keys: changed promise ownership and cross-story/cross-epic reach determine level before any branch loads.

Classify blast radius first

Treat an explicit --level story|epic|project as a candidate, then verify it against the changed promises:

Level	Fully contained change
story	One story; no shared seam, sibling story, epic structure, or product promise changes
epic	Multiple stories or epic IA/experience-chain/structure; no strategic or product-contract change
project	Direction, paid promise, differentiator, project architecture, or cross-epic contract changes

Escalate until the level contains every affected promise. Never preserve a narrower requested level by leaving downstream truth stale. Record the classification and affected artifacts in the adjustment report.

Load exactly one branch

Before mutating any artifact, run:

python3 .speck/scripts/context/speck_context.py adjust --select level=<story|epic|project>

This emits exactly one template and one of references/story.md, references/epic.md, or references/project.md; sibling branches are forbidden.

Common contract

Downgrade the affected unit to NO-SHIP or its lowest still-proven state before implementation.
Re-spec only the deliberate delta; do not silently overwrite validated truth.
Conserve every affected promise: remap it, add a new PRM row, or retire it through a DEC.
Append a decision entry describing the change and alternatives; a replaced decision uses Supersedes: DEC-####.
Re-enter the first affected canonical planning slot. Re-plan, regenerate tasks, run story analysis when required, and re-implement every affected story.
Run decorrelated /speck-audit and the level-specific validation on the changed behavior. A document-only adjustment cannot restore readiness.
Write the dated adjustment report, run its template validation and truth stamp as separate direct commands after the last mutation, then regenerate /project-state.
Restore readiness only from fresh evidence.

---name: adjustdescription: Re-engineers validated work after deliberate change. Use after validation to rebuild and re-prove a redesign or pivot.---# adjustCanonical adjustment engine for intentional changes to validated or shipped work. Defects with no promise change route to `/harden`.Cheap keys: changed promise ownership and cross-story/cross-epic reach determine `level` before any branch loads.## Classify blast radius firstTreat an explicit `--level story|epic|project` as a candidate, then verify it against the changed promises:| Level | Fully contained change ||-------|------------------------|| story | One story; no shared seam, sibling story, epic structure, or product promise changes || epic | Multiple stories or epic IA/experience-chain/structure; no strategic or product-contract change || project | Direction, paid promise, differentiator, project architecture, or cross-epic contract changes |Escalate until the level contains every affected promise. Never preserve a narrower requested level by leaving downstream truth stale. Record the classification and affected artifacts in the adjustment report.## Load exactly one branchBefore mutating any artifact, run:```bashpython3 .speck/scripts/context/speck_context.py adjust --select level=<story|epic|project>```This emits exactly one template and one of `references/story.md`, `references/epic.md`, or `references/project.md`; sibling branches are forbidden.## Common contract1. Downgrade the affected unit to `NO-SHIP` or its lowest still-proven state before implementation.2. Re-spec only the deliberate delta; do not silently overwrite validated truth.3. Conserve every affected promise: remap it, add a new PRM row, or retire it through a DEC.4. Append a decision entry describing the change and alternatives; a replaced decision uses `Supersedes: DEC-####`.5. Re-enter the first affected canonical planning slot. Re-plan, regenerate tasks, run story analysis when required, and re-implement every affected story.6. Run decorrelated `/speck-audit` and the level-specific validation on the changed behavior. A document-only adjustment cannot restore readiness.7. Write the dated adjustment report, run its template validation and truth stamp as separate direct commands after the last mutation, then regenerate `/project-state`.8. Restore readiness only from fresh evidence.

Frequently asked questions

Adjust