Stats
Actions
Tags
From ds
Capture a bug report or feature request as a structured issue file under 00-docs/01-issues. Use when the user reports a problem or asks to "create an issue for ...".
How this skill is triggered — by the user, by Claude, or both
Slash command
/ds:create-issueThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Detect that the user is reporting a problem or asking to create an issue (e.g. "I found these problems", "saw an issue", "these things are wrong", "create an issue for").
00-docs/01-issues/ exists in the current project, write the issue there.00-docs/ does not exist, ask the user where to write the issue.git config --get user.name in the current repo.date +%Y-%m-%d (don't write it from memory); use it for both date and last_updated.YYYY-MM-DD-<slug>.md in the target directory.date and last_updated, the git user for owner, and the confirmed issue title.---
date: YYYY-MM-DD
owner: "<name>"
repository: "<repo>"
topic: "<Issue Title> — Issue Brief"
status: draft
last_updated: YYYY-MM-DD
---
# <Issue Title> — Issue Brief
## Problem
- Current behavior:
- Pain:
- Desired outcome:
## Scope
- In scope:
- Out of scope:
## Affected areas
- Routes / screens / modules:
- Key states (loading / empty / error):
## Data / sources
- System of record:
- Read/write paths:
## Rules / validation
- R1:
- R2:
## Testing
- Unit tests:
- Manual QA steps:
## Open questions
- Q1:
- Q2:
npx claudepluginhub jjjona/agentic-work --plugin dsGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.