open-issue
File a product issue on the board as the PO: check the product and the open issues for a duplicate, choose kind, priority, title and description yourself, and…
Skill by vladmesh
Chalk Labs
Need help deploying open-issue?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/vladmesh-open-issue
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 26, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/open-issue
What's inside
- Skill name
open-issue- Description
- File a product issue on the board as the PO: check the product and the open issues for a duplicate, choose kind, priority, title and description yourself, and create it with `ummanu issue create` without asking the owner first. Use on requests like 'file an issue', 'add this to the backlog', 'open an issue', `$open-issue`.
- License
- Apache-2.0
- Instructions
- 51 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
# Open Issue An issue is a durable record on the product's board: a bug, a feature, a question or an improvement the product owes. It is input for future sprints, not a plan. Your work ends at the created issue; you do not cut cards, promote it to a sprint or start work on it. ## 1. Find the product and check for a duplicate ```bash python3 -P -m ummanu product list python3 -P -m ummanu issue list --product <product> python3 -P -m ummanu issue show --ref <issue-ref> ``` If an open issue already covers the problem, do not file a second one. Add what is new to it instead: ```bash python3 -P -m ummanu issue append --role po --ref <issue-ref> \ --reason "<why this block is added>" --body-file <file> ``` ## 2. Choose the fields You choose every field yourself; there is no owner confirmation before create. - `--kind`: `bug`, `feature`, `question` or `improvement`. - `--priority`: `P0` to `P3`. Pick the one that fits; the owner may change it later (`issue update-priority`). - `--title`: one line that names the problem, not the fix. - `--description`: what is observed or wanted, the evidence (commands, outputs, refs) and what is deliberately out of it. Enough for an observer who was not in this conversation. ## 3. Create it ```bash python3 -P -m ummanu issue create --role po --product <product> \ --kind <kind> --priority <P0-P3> --title "<title>" --description "<description>" \ --request-id <stable-id> ``` `--request-id` makes a retry safe: repeating the command with the same id does not create a second issue. Report the issue reference the command prints back to the owner. ## Later changes - Priority: `issue update-priority --role po --ref <ref> --priority <P0-P3> --reason "<why>"`. - Title or kind: `issue edit --role po --ref <ref> --title "<title>" --kind <kind> --reason "<why>"` (either or both). - Close: `issue close --role po --ref <ref> --reason resolved|invalid|duplicate|wont_do`. - Reopen a closed one: `issue reopen --role po --ref <ref> --reason "<why>"`.
From vladmesh/ummanu, Apache-2.0.
More from vladmesh/ummanu
- 0.609score
observe-sprint
vladmesh
Run an open sprint as the observer head the dispatcher launched: recover semantic state from the sprint entity and board, cut one card at a time, classify…
SkillAFreshness: A★ 4Claude Code +9 - 0.609score
retro
vladmesh
The retro agent's procedure — walk fresh head transcripts and the memory search log, find concrete failures (an answer given from a canon fact without a…
SkillAFreshness: A★ 4Claude Code +9 - 0.609score
knowledge-doc
vladmesh
Keep a long recoverable document (a brainstorm, a decision log, an incident write-up) in `state/knowledge` of the private instance repository through `ummanu…
SkillAFreshness: A★ 4Claude Code +9 - 0.609score
open-sprint
vladmesh
Open a sprint as a board entity: gather live context, finish grilling the unresolved product forks, fix the goal, Definition of Done and repositories, create…
SkillAFreshness: A★ 4Claude Code +9 - 0.606score
curate
vladmesh
The memory curator's procedure — pull durable facts out of fresh transcripts, deduplicate them, and write them into the canon through `curator memory-write`.
SkillAFreshness: A★ 4Claude Code +9 - 0.331score
steward
vladmesh
No description from the publisher yet.
SkillAFreshness: A★ 4Claude Code +9
Signals
- Stars
- 4
- Forks
- 0
- Open issues
- 3
- Last commit (this folder)
- Oct 20, 2026 (11 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- Apache-2.0
- Repository
- github.com/vladmesh/ummanu
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from vladmesh
- 0.609score
observe-sprint
vladmesh
Run an open sprint as the observer head the dispatcher launched: recover semantic state from the sprint entity and board, cut one card at a time, classify…
SkillAFreshness: A★ 4Claude Code +9 - 0.609score
retro
vladmesh
The retro agent's procedure — walk fresh head transcripts and the memory search log, find concrete failures (an answer given from a canon fact without a…
SkillAFreshness: A★ 4Claude Code +9 - 0.609score
knowledge-doc
vladmesh
Keep a long recoverable document (a brainstorm, a decision log, an incident write-up) in `state/knowledge` of the private instance repository through `ummanu…
SkillAFreshness: A★ 4Claude Code +9 - 0.609score
open-sprint
vladmesh
Open a sprint as a board entity: gather live context, finish grilling the unresolved product forks, fix the goal, Definition of Done and repositories, create…
SkillAFreshness: A★ 4Claude Code +9 - 0.606score
curate
vladmesh
The memory curator's procedure — pull durable facts out of fresh transcripts, deduplicate them, and write them into the canon through `curator memory-write`.
SkillAFreshness: A★ 4Claude Code +9
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get open-issue running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
open-issue skill. Agent Mart. https://agentmart.dev/skills/vladmesh-open-issue (last updated 2026-10-24)