issue-discovery

Guide staff engineers through multi-step issue discovery with session persistence.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/ctxr-dev/agent-staff-engineer --skill issue-discovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-discovery
Source: https://github.com/ctxr-dev/agent-staff-engineer/tree/main/skills/issue-discovery
Command: npx skills add https://github.com/ctxr-dev/agent-staff-engineer --skill issue-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides staff engineers through the initial issue discovery process when there is no resolvable issue reference. It captures decisions, defers tracker mutations to tracker-sync, and ensures a safe, auditable handoff to the dev loop.

Core Features & Use Cases

  • Orchestrates a multi-step intake interview that surfaces project targets, existing issues, and umbrella needs.
  • Delegates all tracker mutations to tracker-sync and uses release-tracker for umbrella creation when configured.
  • Maintains ephemeral session state under .development/local/issue-discovery and resumes cleanly across restarts.

Quick Start

Initiate issue discovery when there is no resolvable issue reference and follow the guided prompts to produce a handoff.

Frequently Asked Questions about issue-discovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start the dev loop when there is no resolvable issue reference?

Issue discovery guides staff engineers through a multi-step intake interview to capture project targets, select existing issues, and link umbrellas before safely handing off to the dev loop.

What is the best way to manage issue intake across multiple project trackers?

Issue discovery orchestrates intake across multiple trackers by targeting projects, selecting or creating issues, and deferring all tracker mutations to tracker-sync for a safe, auditable handoff.

How does session persistence work during the issue discovery workflow?

Session state is maintained locally under .development/local/issue-discovery, allowing the guided intake process to resume cleanly across restarts with explicit user gates and rollback rules.

Can I link umbrella issues during the initial issue discovery process?

Yes, issue discovery handles umbrella linking during intake and delegates umbrella creation to release-tracker when configured, ensuring proper project hierarchy before starting the dev loop.

Do I need tracker-sync to create issues during the intake process?

Yes, issue discovery captures all intake decisions but delegates actual tracker mutations to tracker-sync, ensuring mutations are handled safely and auditably rather than directly modifying the tracker.

What happens if I need to roll back decisions during the issue discovery workflow?

Issue discovery implements a guarded, multi-step state machine with explicit user gates, clear rollback rules, and archival capabilities to safely reverse intake decisions before the dev loop handoff.