Agent skill

phase3-ticket-investigation

Investigate Phase 3 tickets to clarify scope and determine implementation vs. defer vs. close

majiayu000534★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill phase3-ticket-investigation --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 5 KB
Bundled scripts: none
Version: 1
Requires: opencode,claude
Path: skills/analysis/phase3-ticket-investigation/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

<!-- BEGIN:compound:skill-managed --> # Purpose Investigate Phase 3 tickets (Orchestration, CLI, Scheduling, Monitoring, Testing) to clarify scope and provide implementation recommendation. # When To Use - Manager assigns Phase 3 ticket investigation - Ticket has empty/unclear body but tags indicate a Phase 3 component - Need to decide if ticket should be scoped, deferred, or closed # Procedure ## 1. Gather Context - List all Phase 3 tickets: `loom ticket list --tag phase3` - Read ROADMAP.md to understand Phase 3 goals and components - Check each Phase 3 ticket status and body content ## 2. Check Component Status ### For Orchestration (vp-cf95) - Check if ExecutionEngine exists in `src/vibe_piper/orchestration/` - Verify orchestration tests in `tests/test_orchestration.py` - Look for implementation commits in git log ### For CLI (vp-6cf1) - Check CLI commands in `src/vibe_piper/cli/` - Verify CLI tests in `tests/cli/` - Check if commands are registered and working ### For Scheduling (vp-7d49) - Check scheduling module in `src/vibe_piper/scheduling/` - Verify scheduling tests in `tests/scheduling/` - Check test pass rate ### For Monitoring (vp-f17e) - Check monitoring module in `src

What's inside
Steps it walks through
  1. 1. Gather Context
  2. 2. Check Component Status
  3. For Orchestration (vp-cf95)
  4. For CLI (vp-6cf1)
  5. For Scheduling (vp-7d49)
  6. For Monitoring (vp-f17e)
  7. For Testing (vp-0429)
  8. 3. Analyze Roadmap Context
  9. 4. Determine Recommendation
  10. Implement If:
  11. Defer If:
  12. Close If:
  13. 5. Document Findings
  14. 6. Communicate to Manager
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the phase3-ticket-investigation skill do?

Investigate Phase 3 tickets to clarify scope and determine implementation vs. defer vs. close

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill phase3-ticket-investigation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going