Skip to content

jabrena/plinth / skills/004-commands-installation

004-commands-installation

Verified

Use when you need to install the embedded project commands into command directories (.github/commands, .claude/commands, .cursor/command, .codex/commands), selecting the destination interactively and copying the embedded command definitions from project assets. This should trigger for requests such as Install embedded commands; Bootstrap .cursor/command; Bootstrap .claude/commands; Copy project commands; Install project command suite. Part of Plinth Toolkit

assets/commands/close-spec.md

View on GitHub
---
description: 'Archive a completed OpenSpec change by name.'
argument-hint: '[openspec-change]'
model: 'inherit'
agent: 'plinth-architect'
tools:
  - 'Read'
  - 'Bash'
metadata:
  author: 'Juan Antonio Breña Moral'
  version: '0.19.0'
---

# close-spec

Archive an OpenSpec change by name, using the OpenSpec CLI, so completed changes can be reconciled and removed from the active change list.

## Usage

```text
/close-spec <change-name>
```

## Inputs

- `<change-name>`: the OpenSpec change name to archive (for example `add-close-spec-command`)

## Owner

`@plinth-architect`

## Workflow

1. Validate the argument is present.
   - If missing, print usage: `/close-spec <change-name>` and stop.
2. Verify the OpenSpec CLI is available (for example, `openspec --version`).
   - If OpenSpec cannot be executed, report the missing prerequisite and provide a short hint to install/enable OpenSpec.
3. Verify the change exists before attempting to archive it.
   - Prefer checking `openspec list` and matching `<change-name>`, or
   - Use `openspec show <change-name>` and treat “not found” as an unknown-change error.
   - If the change is unknown, report that the change was not found and suggest running `openspec list`.
4. From the `documentation/` working directory, execute the equivalent of:
   - `openspec archive <change-name>`
5. If the archive command fails, surface the OpenSpec CLI output and stop (do not claim success).
6. If the archive command succeeds, report a success message that includes `<change-name>`.

## Safeguards

- Do not guess or auto-correct the change name.
- Do not claim success when `openspec archive` fails; surface the CLI output.
- Do not run `openspec archive` unless the change exists.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall