github-issue-create

Create Agent Task Workflow

This workflow guides you through creating a detailed GitHub issue using the gemini_agent_workflow.md template. This is the mandatory first step when a user requests a new feature or complex change.

Trigger

Use this workflow when the user asks to "create a task," "plan a feature," "spec out a ticket," or "create a workflow issue."

---

Phase 1: Deep Research & Analysis (Using Subagent)

1. Analyze User Request: Identify the core goal and any implicit requirements.
2. Delegate to Subagent: ALWAYS use the codebase_investigator subagent to perform the deep research. Pass it the user's objective and ask it to:
   • Walk through the feature as a user and define the Browser Click Path (relevant routes, exact steps).
   • Investigate Schema & Database: Check project configuration (package.json under "agents" key, or docs/project.json) for paths.db and paths.types. If configured, use those paths to search for database/migration files and types/data models. If not configured, dynamically search for directories named db, prisma, database, or types using codebase search tools.
   • Identify all relevant files (Page components, API routes, Service logic) that need modification to ensure complete coverage.
3. Review Subagent Report: Use the structured report provided by the codebase_investigator to inform the implementation plan.

---

Phase 2: Formulate & Refine Implementation Plan (Subagent-Driven)

Before creating any issue on GitHub, the implementation plan must be drafted, scrutinized by a subagent, and interactively approved by the user.

1. Draft Initial Plan:

   • Synthesize the research and draft an initial implementation plan.
   • Break down the work into logical, atomic steps with precise reasons for each step.
   • Fill out all template fields (Proposed Changes, Testing Strategy, Browser Click Path, i18n/translations, Performance/Edge cases).

2. Subagent Grilling & Refinement:

   • Mandatory: ALWAYS delegate the initial plan to a specialized general-purpose subagent to grill it.
   • Instruct the subagent to locate potential architectural flaws, edge cases, missing translations, verification gaps, and project-rule violations (docs/rules/).
   • The subagent MUST perform all plan refinements, producing a highly secure, detailed, and polished version of the plan.