devflow:build:create-issue

Create Issue

I'll create a detailed issue (Feature/Bug) with codebase analysis and research.

Request: $ARGUMENTS

Reference docs: Load ../references/issue-standards/core-standards.md (always), then the type-specific file based on issue type selected in Step 1:

• Feature → ../references/issue-standards/feature-standards.md + ../references/issue-standards/FEATURE-EXAMPLE.md
• Bug → ../references/issue-standards/bug-standards.md + ../references/issue-standards/BUG-EXAMPLE.md
• Documentation, Chore, Research, Tech Debt → ../references/issue-standards/other-types.md

---

Step 1: Load Configuration and Connect to Backend

Use the build-ops skill to:

1. Load backend configuration from devflow-config.md
2. Connect to the configured issue tracker and discover available projects

The build-ops skill handles all backend-specific operations (Jira, GitLab, GitHub) and enforces parameter validation. See skills/build-ops/SKILL.md.

🚨 CRITICAL: Ask ONE question at a time. Wait for user response before next question.

🚨 CRITICAL: MCP handles authentication - NEVER ask for URL/cloudId/credentials!

---

Project Selection:

Use the build-ops skill's project discovery to list available projects.

Ask ONLY: "Which project?" [Display projects from backend]

WAIT. Store selected project identifier.

---

Issue Type:

Ask ONLY: "What type of issue?"

Options:

1. Feature (new functionality)
2. Bug (something broken)
3. Documentation (docs update)
4. Chore (housekeeping, maintenance)
5. Research (investigation, spike)
6. Technical Debt (refactoring, cleanup)

WAIT.

[Map to issue types]:

• Jira: Feature → "Executable Spec", Bug → "Bug", Others → "Task"
• GitLab: All create as issues with appropriate labels
• GitHub: All create as issues with appropriate labels

[For Jira: Call mcp__atlassian__getJiraProjectIssueTypesMetadata to verify type exists]

---

Title:

[Suggest title based on description]

Ask ONLY: "Use this title: '[suggested]' or provide your own?"

WAIT. Store title.

---

Priority:

Ask ONLY: "Priority? (High/Medium/Low)"

WAIT. Default Medium if unclear.

---

Step 2: Analyze Codebase

[Use Grep/Glob/Read to find]:

• Existing libraries/tools (search pyproject.toml, package.json, Cargo.toml, go.mod, etc.)
• Related components/files for this feature/bug
• Existing patterns (imports, error handling, logging, module structure)
• Integration points (where this connects)

Present findings with file paths.

---

Step 3: Research (If Needed)

[Based on user's description and codebase analysis from Step 2]:

If feature requires library/tool NOT in codebase:

Say: "This feature needs [library X]. I don't see it in the project. Research options with Context7?"

Ask ONLY: "Yes or No?"

WAIT.

If Yes:

• mcp__context7__resolve-library-id
• mcp__context7__get-library-docs

Summarize strategic insights (which library, why, trade-offs) - NOT API docs.

If feature uses existing libraries:

• Skip research
• Use existing patterns from codebase

---

Step 4: Draft Issue

Draft the issue following the standards from the loaded reference files:

• Core standards (always): Outcomes vs Implementation principle, priority guidelines, labels
• Type-specific standards: Required structure and sections for the selected issue type
• Examples (Feature/Bug): Follow the example file as a formatting reference

Core principle: WHAT (outcomes, capabilities), not HOW (implementation). See core-standards.md.

---

Step 5: Labels

[Extract from description + analysis]

Say: "Suggested: [label1], [label2], [label3]"

Ask ONLY: "Use these or edit/add?"

WAIT. Store labels.

---

Step 6: Review & Approve

Show complete preview:

• Backend: [Jira/GitLab/Local]
• Project: [KEY - Name]
• Type: [Feature/Bug/etc.]
• Title: [title]
• Priority: [priority]
• Labels: [labels]
• Full description: [complete text]

Ask ONLY: "Create this issue?"

Options: "Yes / Edit / Cancel"

⏸️ WAIT for explicit "Yes"

• Edit: Ask changes, revise, show again
• Cancel: Stop
• Yes: Proceed

---

Step 7: Create

[Only if approved]

Use the build-ops skill to create the issue in the configured backend with:

• Project: [selected project from Step 1]
• Type: [selected type]
• Title: [approved title]
• Description: [approved description]
• Labels: [approved labels]
• Priority: [selected priority]

The build-ops skill handles all backend-specific creation logic and enforces parameter validation. See skills/build-ops/SKILL.md.

Return: Issue key/number, URL, suggested branch name.

---

Rules

Never:

• Create without approval
• Use "Story" in Jira (must be "Executable Spec")
• Skip codebase analysis
• Ask multiple questions at once

Always:

• Reference examples (see references/ directory)
• Wait for responses at each step
• Focus on outcomes, not implementation

References

• ../references/issue-standards/core-standards.md - Core principles (always load)
• ../references/issue-standards/feature-standards.md - Feature issue structure
• ../references/issue-standards/bug-standards.md - Bug issue structure
• ../references/issue-standards/other-types.md - Documentation, Chore, Research, Tech Debt
• ../references/issue-standards/FEATURE-EXAMPLE.md - Feature example
• ../references/issue-standards/BUG-EXAMPLE.md - Bug example