Loading...
Loading...
Found 169 Skills
Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.
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.
Triage GitHub issues by applying type, effort, priority, and area labels. Runs in an isolated context to avoid polluting the main conversation with issue details. Delegates to a specialized triage agent with label validation hooks.
Use when the user asks to create a GitHub issue from the current conversation context (e.g., "new issue", "create issue", "file an issue", bug/feature request) with a target repo given or auto-detected, and gh CLI is available/authenticated.
Use when creating, searching, updating, or managing GitHub issues via CLI. Triggers: "issue", "create issue", "gh issue", "task tracking", "context", "handoff", "resume task", "session context", "save progress", "active tasks", "in-progress", "my tasks", "open issues". Covers: gh commands, bulk operations, JSON/jq, search filters, issue-to-PR workflow, AI session context storage, task workflow with labels.
Create GitHub Issue from spec documents — Auto-generate structured Feature Issues from specifications. Analyzes spec documents (requirement.md, design.md, tasks.md) in .specs/{feature}/ and generates a structured Feature Issue via gh issue create. Best used with specs created by spec-generator. English triggers: - "Create issue from spec", "Register spec as issue" - "Convert spec to GitHub issue", "Publish spec to issue" - After spec-generator: "Turn this into an issue" 日本語トリガー: - 「仕様書をIssueにして」「Issueに登録して」「specからIssue作成」 - 「仕様書からIssue生成」「specをIssueに変換」 - spec-generator完了後に「これをIssueにして」「Issueにして」
Create a feature branch in a git worktree from a GitHub issue
Report a bug in the compound-engineering plugin
Use when bootstrapping skill-loop in a repository, creating a GitHub issue loop starter, or writing and updating skill-loop.yml and starter skills.
Replicate and validate a GitHub issue by spinning up Archon, analyzing the issue, and systematically testing all described symptoms using browser automation. Use when: User wants to reproduce a bug, validate a GitHub issue, confirm a reported problem, or investigate whether an issue is real before working on a fix. Triggers: "replicate issue", "reproduce issue", "validate issue", "confirm bug", "test issue", "can you reproduce", "try to replicate", "verify the bug". Capability: Checks out main, pulls latest, starts Archon, reads the GitHub issue, then uses agent-browser to systematically test every symptom and produce a findings report. NOT for: Fixing issues (use /archon or /exp-piv-loop:fix-issue), general UI testing (use /validate-ui).
Create a detailed refactor plan with tiny commits through user interviews, then file it as a GitHub issue. Use this when the user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
Decompose a PRD and/or SPEC into implementable Issues and create them in your chosen platform (GitHub, Local, or Baidu iCafe). Use after /prd (and optionally /prd-to-spec) to turn requirements into actionable tickets. Triggers on: create issues, to-issues, 创建issue, 拆解issue, 生成卡片, 创建卡片, generate issues from PRD, issues from spec.