/issues
View and manage deferred issues tracked across sessions
$ npx -y skills add lgbarn/shipyard --agent claude-codeShips with shipyard. Installing the plugin gets this command.
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/issues
Context preview
What this command does when you run it.
View and manage deferred issues tracked across sessions
Command definition
issues.mddescription: "View and manage deferred issues tracked across sessions"
disable-model-invocation: true
argument-hint: "[--add <description>] [--resolve <id>] [--list]"
/shipyard:issues - Issue Tracking
You are executing the Shipyard issue tracking workflow. Follow these steps precisely.
<prerequisites>
Step 1: Check State Exists
Check if `.shipyard/` directory exists.
- **If it does not exist:**
Display: > "No Shipyard project detected. Run `/shipyard:init` to get started." Stop here.
Step 2: Ensure ISSUES.md Exists
Check if `.shipyard/ISSUES.md` exists.
- **If it does not exist**, create it with this template:
# Shipyard Issues
Deferred enhancements and non-blocking findings tracked across sessions.
## Open Issues
| ID | Severity | Source | Description | Date |
|----|----------|--------|-------------|------|
## Resolved Issues
| ID | Description | Resolved | Resolution |
|----|-------------|----------|------------|
Step 3: Parse Arguments
- `--add <description>`: Add a new issue. Ask for severity (high/medium/low) if not obvious from context. Auto-increment ID from highest existing ID + 1. Set source to "manual" and date to current timestamp.
- `--resolve <id>`: Move the issue from Open to Resolved. Ask for a brief resolution note.
- `--list` (default when no arguments): Display current issues.
</prerequisites>
<execution>
Step 4: Execute Action
For --add:
Append a new row to the Open Issues table:
| {next_id} | {severity} | manual | {description} | {YYYY-MM-DD} |Confirm: > "Issue #{id} added: {description}"
For --resolve:
1. Find the issue by ID in the Open Issues table 2. Remove it from Open Issues 3. Add it to Resolved Issues with resolution timestamp and note 4. Confirm: > "Issue #{id} resolved: {resolution_note}"
For --list (default):
Display issues grouped by severity:
Shipyard Issues
═══════════════
High Priority ({count})
#{id}: {description} [source: {source}, {date}]
Medium Priority ({count})
#{id}: {description} [source: {source}, {date}]
Low Priority ({count})
#{id}: {description} [source: {source}, {date}]
Total: {open_count} open, {resolved_count} resolvedIf no open issues exist: > "No open issues. Clean slate!"
</execution>
<output>
Step 5: Suggest Next Action
If there are high-priority issues: > "Consider addressing high-priority issues before your next `/shipyard:build` or `/shipyard:ship`."
If viewing issues during planning: > "Open issues relevant to the current phase can be incorporated into `/shipyard:plan`."
</output>
Read more
description: "View and manage deferred issues tracked across sessions" disable-model-invocation: true argument-hint: "[--add <description>] [--resolve <id>] [--list]"
/shipyard:issues - Issue Tracking
You are executing the Shipyard issue tracking workflow. Follow these steps precisely.
<prerequisites>
Step 1: Check State Exists
Check if `.shipyard/` directory exists.
- **If it does not exist:**
Display: > "No Shipyard project detected. Run `/shipyard:init` to get started." Stop here.
Step 2: Ensure ISSUES.md Exists
Check if `.shipyard/ISSUES.md` exists.
- **If it does not exist**, create it with this template:
# Shipyard Issues Deferred enhancements and non-blocking findings tracked across sessions. ## Open Issues | ID | Severity | Source | Description | Date | |----|----------|--------|-------------|------| ## Resolved Issues | ID | Description | Resolved | Resolution | |----|-------------|----------|------------|
Step 3: Parse Arguments
- `--add <description>`: Add a new issue. Ask for severity (high/medium/low) if not obvious from context. Auto-increment ID from highest existing ID + 1. Set source to "manual" and date to current timestamp.
- `--resolve <id>`: Move the issue from Open to Resolved. Ask for a brief resolution note.
- `--list` (default when no arguments): Display current issues.
</prerequisites>
<execution>
Step 4: Execute Action
For --add:
Append a new row to the Open Issues table:
| {next_id} | {severity} | manual | {description} | {YYYY-MM-DD} |Confirm: > "Issue #{id} added: {description}"
For --resolve:
1. Find the issue by ID in the Open Issues table 2. Remove it from Open Issues 3. Add it to Resolved Issues with resolution timestamp and note 4. Confirm: > "Issue #{id} resolved: {resolution_note}"
For --list (default):
Display issues grouped by severity:
Shipyard Issues
═══════════════
High Priority ({count})
#{id}: {description} [source: {source}, {date}]
Medium Priority ({count})
#{id}: {description} [source: {source}, {date}]
Low Priority ({count})
#{id}: {description} [source: {source}, {date}]
Total: {open_count} open, {resolved_count} resolvedIf no open issues exist: > "No open issues. Clean slate!"
</execution>
<output>
Step 5: Suggest Next Action
If there are high-priority issues: > "Consider addressing high-priority issues before your next `/shipyard:build` or `/shipyard:ship`."
If viewing issues during planning: > "Open issues relevant to the current phase can be incorporated into `/shipyard:plan`."
</output>
A Claude Code plugin for structured project execution. Plan work in phases, build with parallel agents and TDD, review with security audits and quality gates, and ship with confidence.
Repo: lgbarn/shipyard
Other commands on shipyard.
- /audit
On-demand security audit — OWASP, secrets, dependencies, IaC security
Open command - /brainstorm
Explore requirements through Socratic dialogue and capture project definition
Open command - /build
Execute plans using fresh subagents with review gates
Open command - /cancel
Pause in-progress work with a checkpoint
Open command - /debug
Investigate bugs and failures with systematic root-cause analysis
Open command - /doctor
Check Shipyard plugin health and dependencies
Open command

