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/update-issue.md

View on GitHub
---
description: 'Update an issue description with structured, evidence-backed content.'
argument-hint: '[issue-url]'
model: 'inherit'
agent: 'plinth-business-analyst'
tools:
  - 'Read'
  - 'Bash'
metadata:
  author: 'Juan Antonio Breña Moral'
  version: '0.19.0'
---

# update-issue

Update an existing project issue description with structured, evidence-backed content.

## Usage

```text
/update-issue <issue> [<source>] [<tracker>]
```

## Accepted Inputs

- Existing GitHub or Jira issue number, key, or URL
- Optional source notes, supporting discussion, user story, acceptance criteria, or file path
- Optional tracker selection: GitHub or Jira

## Owning Agent

`@plinth-business-analyst`

## Associated Skills

- `043-planning-github-issues`
- `044-planning-jira`
- `045-planning-azure-devops`
- `014-agile-user-story` when user-story refinement is required

## Workflow

1. Load the current issue description and relevant discussion before drafting changes.
2. Confirm the requested update scope and the source material authority.
3. Use `014-agile-user-story` when the update needs user-story, acceptance-criteria, or Gherkin-style structure.
4. Draft the updated issue body without inventing requirements.
5. Present the proposed body before overwriting the existing issue description.
6. Update the issue in the selected tracker after approval.
7. Report the issue identifier and URL.

## Output

- Updated structured issue description
- Acceptance criteria or user-story scenario when applicable
- Updated GitHub/Jira issue reference

## Safeguards

- Do not invent requirements, acceptance criteria, or comments.
- Do not expose tracker credentials or tokens.
- Do not overwrite an issue body without showing the proposed replacement.
- Preserve relevant existing issue content unless the user explicitly asks to remove it.
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