Skip to content
cccskills
FreePublished on GitHub

openspec-archive-change

Archive a completed RIPDPI OpenSpec change through the fail-closed taskctl lifecycle.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Archive an OpenSpec change

Use this skill only when implementation is complete and the user asks to finalize a change.

  1. Resolve the active change with ./taskctl openspec cli list --json and its linked portfolio task with ./taskctl list --json.
  2. Run ./taskctl verify <task-id> --archive-ready. Stop on open mdtask steps, invalid OpenSpec artifacts, missing exact-SHA evidence, or any required/blocked evidence category.
  3. Require portfolio status review; never treat an agent checkbox as acceptance.
  4. Run ./taskctl openspec archive <change-name>. Never call the upstream archive command directly, pass --no-validate, move a change directory manually, or proceed after a warning.
  5. Run ./taskctl close prepare <task-id> --outcome done --evidence "<concise evidence summary>".
  6. Stop and ask for the terminal-state commit. close purge is a later, separately committed step.

For a dropped task, do not archive incomplete behavior deltas as completed. Prepare dropped with an explicit reason and preserve the active change until the owner decides whether to revise or remove it.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

RIPDPI's own Compose conventions: ViewModel pattern, Route/Screen split, DataStore->StateFlow, RipDpiThemeTokens. Use for how this app does Compose, not generic Compose API questions (see compose).

The English summary is being prepared. Showing the original description.

po4yka/RIPDPI81Updated Oct 20, 2026

ADB-based RIPDPI device/emulator debugging: build/install/launch, logcat filtering, fixture port-forwarding, instrumented tests, crash/ANR triage. Use when debugging on a real device or emulator.

The English summary is being prepared. Showing the original description.

po4yka/RIPDPI81Updated Oct 20, 2026

RIPDPI Appium launch-contract reference: start routes and permission/service/data presets. Use when a test launches to the wrong screen or a new automation route is added. General flakiness: appium-test-debug.

The English summary is being prepared. Showing the original description.

po4yka/RIPDPI81Updated Oct 20, 2026

RIPDPI Appium test authoring: page objects, resource-id locators, assertions, wait tiers. Use when writing a new Appium test or page object, or adding coverage for a new screen.

The English summary is being prepared. Showing the original description.

po4yka/RIPDPI81Updated Oct 20, 2026

RIPDPI Appium failure triage: flaky tests, locator/session/wait issues, screenshot and element-tree debugging. Use when an Appium test fails or is flaky.

The English summary is being prepared. Showing the original description.

po4yka/RIPDPI81Updated Oct 20, 2026

Add or modify a GitHub Actions job. Use when editing a file under .github/workflows/. Not for running a workflow locally (local-ci-act) or release signing (release-signing).

The English summary is being prepared. Showing the original description.

po4yka/RIPDPI81Updated Oct 20, 2026

See all skills by po4yka

Report a problem with this skill