Loading...
Loading...
Issue creation workflow for Agent Teams Lite following the issue-first enforcement system. Trigger: When creating a GitHub issue, reporting a bug, or requesting a feature.
npx skill4agent add gentleman-programming/sdd-agent-team issue-creationstatus:needs-reviewstatus:approved1. Search existing issues for duplicates
2. Choose the correct template (Bug Report or Feature Request)
3. Fill in ALL required fields
4. Check pre-flight checkboxes
5. Submit → issue gets status:needs-review automatically
6. Wait for maintainer to add status:approved
7. Only then open a PR linking this issue.github/ISSUE_TEMPLATE/bug_report.ymlbugstatus:needs-review| Field | Description |
|---|---|
| Pre-flight Checks | Checkboxes: no duplicate + understands approval workflow |
| Bug Description | Clear description of the bug |
| Steps to Reproduce | Numbered steps to reproduce |
| Expected Behavior | What should have happened |
| Actual Behavior | What happened instead (include errors/logs) |
| Operating System | Dropdown: macOS, Linux variants, Windows, WSL |
| Agent / Client | Dropdown: Claude Code, OpenCode, Gemini CLI, Cursor, Windsurf, Codex, Other |
| Shell | Dropdown: bash, zsh, fish, Other |
| Field | Description |
|---|---|
| Relevant Logs | Log output (auto-formatted as code block) |
| Additional Context | Screenshots, workarounds, extra info |
gh issue create --template "bug_report.yml" \
--title "fix(scripts): setup.sh fails on zsh with glob error" \
--body "
### Pre-flight Checks
- [x] I have searched existing issues and this is not a duplicate
- [x] I understand this issue needs status:approved before a PR can be opened
### Bug Description
Running setup.sh on zsh throws a glob error when no matching files exist.
### Steps to Reproduce
1. Clone the repo
2. Run \`./scripts/setup.sh\` in zsh
3. See error: \`zsh: no matches found: skills/*\`
### Expected Behavior
The script should handle missing glob matches gracefully.
### Actual Behavior
Script crashes with glob error.
### Operating System
macOS
### Agent / Client
Claude Code
### Shell
zsh
### Relevant Logs
\`\`\`
zsh: no matches found: skills/*
\`\`\`
".github/ISSUE_TEMPLATE/feature_request.ymlenhancementstatus:needs-review| Field | Description |
|---|---|
| Pre-flight Checks | Checkboxes: no duplicate + understands approval workflow |
| Problem Description | The pain point this feature solves |
| Proposed Solution | How it should work from the user's perspective |
| Affected Area | Dropdown: Scripts, Skills, Examples, Documentation, CI/Workflows, Other |
| Field | Description |
|---|---|
| Alternatives Considered | Other approaches or workarounds |
| Additional Context | Mockups, examples, references |
gh issue create --template "feature_request.yml" \
--title "feat(scripts): add Codex support to setup.sh" \
--body "
### Pre-flight Checks
- [x] I have searched existing issues and this is not a duplicate
- [x] I understand this issue needs status:approved before a PR can be opened
### Problem Description
The setup script only configures Claude Code, Gemini CLI, and OpenCode. Codex users have to manually copy skills.
### Proposed Solution
Add a Codex option to setup.sh that links skills to the .codex/ directory.
Example:
\`\`\`bash
./scripts/setup.sh --agent codex
\`\`\`
### Affected Area
Scripts (setup, installation)
### Alternatives Considered
Manually symlinking, but that defeats the purpose of the setup script.
"| Template | Labels added |
|---|---|
| Bug Report | |
| Feature Request | |
| Label | When to apply |
|---|---|
| Issue accepted for implementation — PRs can now be opened |
| Critical bug or urgent feature |
| Important but not blocking |
| Nice to have |
1. New issue arrives with status:needs-review
2. Review the issue — is it valid, clear, and in scope?
3. If YES → add status:approved label
4. If NO → comment with reason, close if needed
5. Contributor can now open a PR linking this issueIs it a bug? → Use Bug Report template
Is it a new feature/improvement? → Use Feature Request template
Is it a question? → Use Discussions, NOT issues
Is it a duplicate? → Link to existing issue, close# Search existing issues before creating
gh issue list --search "keyword"
# Create bug report
gh issue create --template "bug_report.yml" --title "fix(scope): description"
# Create feature request
gh issue create --template "feature_request.yml" --title "feat(scope): description"
# Maintainer: approve an issue
gh issue edit <number> --add-label "status:approved"
# Maintainer: add priority
gh issue edit <number> --add-label "priority:high"