How do I install the Stip Archive skill?

Run npx skillmds@latest add bryann2k/stip-archive 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 Stip Archive safe to use?

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

Which AI agents work with Stip Archive?

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

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Stip Archive?

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

Stip Archive by bryann2k — Agent Skill

Name: Stip Archive
Author: BRYANN2K

File contents

stip-archive

Archive only after current approval, successful acceptance checks and documentation completion. Read status and inspect the intended Git changes. The user invoking this skill requests a local archive commit; it does not authorize a push or deployment.

For a schema-v2 change, read references/orchestration.md. Reconcile actual native sessions, stop further dispatch and ensure every planned contribution is accepted with no active or unknown workers. The main coordinator performs archive; workers do not change lifecycle records or commit. The engine generates a bounded execution summary during archive; review its task/session/model provenance against observed results. The private .workflow/.runtime/ registry remains untracked and outside the archive commit.

Run archive <id> --message <meaningful-message> --paths <exact-source-and-doc-paths-changed-since-start>. The command promotes spec.md to .workflow/specs/<target>.md, moves the complete change to archive and commits those workflow records plus exactly the supplied paths. A new feature normally uses its change id as target; an evolution uses the target selected during explore.

The command refuses stale evidence, changed HEAD, concurrent target-spec edits, staged unrelated work or selected files that already had modifications at apply start. Do not reset, overwrite or absorb other work to satisfy it. Reconcile the Git situation with the user when it cannot be safely separated. If HEAD moved, the engine requires explicit reconciliation/restarting the change; it does not automatically rebase evidence.

Commit hooks run normally. A failed commit restores the workflow transaction and unstages its paths when HEAD did not change. Hook-caused source changes or an already-created unexpected commit require inspection; never claim rollback or success beyond the output.

Read back the archive, accepted spec and Git commit. Report the commit hash and any remaining unrelated work. Never amend the archive immediately to insert its own commit hash; Git history is its locator.

Runtime

Use the Python runtime bundled with this skill, independent of the current directory:

python3 <this-skill-directory>/scripts/workflow.py --root <physical-project-root> <command>

Python 3.10+ and Git are required for implementation and archive. Run --help or <command> --help for exact arguments. The runtime is offline and never installs tools. System/developer instructions, current user intent and environment permissions remain authoritative.

---name: stip-archivedescription: Close a documented workflow change, promote its accepted specification and create a scoped local Git commit.license: Apache-2.0---# stip-archiveArchive only after current approval, successful acceptance checks and documentation completion. Read status and inspect the intended Git changes. The user invoking this skill requests a local archive commit; it does not authorize a push or deployment.For a schema-v2 change, read [references/orchestration.md](references/orchestration.md). Reconcile actual native sessions, stop further dispatch and ensure every planned contribution is accepted with no active or unknown workers. The main coordinator performs archive; workers do not change lifecycle records or commit. The engine generates a bounded execution summary during archive; review its task/session/model provenance against observed results. The private `.workflow/.runtime/` registry remains untracked and outside the archive commit.Run `archive <id> --message <meaningful-message> --paths <exact-source-and-doc-paths-changed-since-start>`. The command promotes spec.md to `.workflow/specs/<target>.md`, moves the complete change to archive and commits those workflow records plus exactly the supplied paths. A new feature normally uses its change id as target; an evolution uses the target selected during explore.The command refuses stale evidence, changed HEAD, concurrent target-spec edits, staged unrelated work or selected files that already had modifications at apply start. Do not reset, overwrite or absorb other work to satisfy it. Reconcile the Git situation with the user when it cannot be safely separated. If HEAD moved, the engine requires explicit reconciliation/restarting the change; it does not automatically rebase evidence.Commit hooks run normally. A failed commit restores the workflow transaction and unstages its paths when HEAD did not change. Hook-caused source changes or an already-created unexpected commit require inspection; never claim rollback or success beyond the output.Read back the archive, accepted spec and Git commit. Report the commit hash and any remaining unrelated work. Never amend the archive immediately to insert its own commit hash; Git history is its locator.## RuntimeUse the Python runtime bundled with this skill, independent of the current directory:```textpython3 <this-skill-directory>/scripts/workflow.py --root <physical-project-root> <command>```Python 3.10+ and Git are required for implementation and archive. Run `--help` or `<command> --help` for exact arguments. The runtime is offline and never installs tools. System/developer instructions, current user intent and environment permissions remain authoritative.

Frequently asked questions

Stip Archive