Issue
ProductivityissueIssue is an Agent Skill for productivity published in the x-cmd/x-cmd repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Issue management for devloop — templates for goal, rule.yml, key-results, and issue lifecycle.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/x-cmd/x-cmd/blob/HEAD/mod/skill0/lib/skill0/skills/issue/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/issue, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
issue
Part of devloop.
New dev issue template
gh issue create --title "<scope>: <short description>" --body "$(cat <<'EOF'
## Goal
<one-line objective>
## Key Results
- [ ] KR-1: <verifiable outcome>
- [ ] KR-2: <verifiable outcome>
## rule.yml
```yaml
goal: "<same as above>"
keyresults:
- kr-1: "<same as above>"
- kr-2: "<same as above>"
rules:
- id: <rule-id>
name: <name>
apply: "<file pattern>"
level: error
desc:
- <criterion>
Screenshots
- Before: <image or "N/A">
- After: <image or "pending"> EOF )"
## Issue lifecycle
| Stage | Action | Comment content |
|-------|--------|-----------------|
| Created | `gh issue create` with template | goal, key-results, rule.yml |
| In progress | Update as work proceeds | progress notes, intermediate screenshots |
| Verified | `x rule check` passes | rule check result, after screenshot |
| Closed | `gh issue close` | commit SHA, final verification summary |
## Completion comment template
gh issue comment --body "$(cat <<'EOF'
Verified
- rule.yml:
- x rule check: PASS
- Before:
- After:
- Commit: EOF )"
## Rules
- **MUST** include `goal` and `keyresults` in every dev issue — no exceptions
- **MUST** post rule.yml as code block in issue body or first comment
- **MUST** screenshot before and after for frontend changes
- **NEVER** close an issue without verification evidence
- Link issues to project board for roadmap visibility