Fix confusing instructions in ticket creation session prompts

[itdove]

Problem

The session prompts for daf jira new and daf git new contain confusing instructions that tell the AI to create tickets using daf jira create or daf git create commands, but this creates ambiguity:

Current prompts say:

• "Create a detailed JIRA Story using the 'daf jira create' command"
• "Create a detailed GitHub/GitLab issue using the 'daf git create' command"

Why this is confusing:

1. Users already ran daf jira new or daf git new to start the session
2. The AI should use the SAME command type that the user used
3. Mentioning both creates uncertainty about which to use
4. The prompt should NOT suggest switching between JIRA and GitHub/GitLab

Files Affected

Based on grep search:

1. devflow/cli/commands/jira_new_command.py (line 878)

   f"3. Create a detailed JIRA {issue_type} using the 'daf jira create' command",

2. devflow/cli/commands/git_new_command.py (line 879)

   f"3. Create a detailed GitHub/GitLab issue{' (' + issue_type + ')' if issue_type else ''} using the 'daf git create' command",

3. devflow/cli/commands/investigate_command.py (lines 547, 554, 662, 670)

   • Multiple mentions of "create issue tracker tickets using 'daf jira create' (for JIRA) or 'daf git create' (for GitHub/GitLab)"
   • This is less critical since investigate sessions allow flexibility

Proposed Changes

For jira_new_command.py

Current (line 878):

3. Create a detailed JIRA {issue_type} using the 'daf jira create' command

Proposed:

3. Create a detailed JIRA {issue_type} using the 'daf jira create' command (same backend as this session)

OR simpler:

3. Create the JIRA {issue_type} using 'daf jira create'

For git_new_command.py

Current (line 879):

3. Create a detailed GitHub/GitLab issue using the 'daf git create' command

Proposed:

3. Create the GitHub/GitLab issue using 'daf git create' (same backend as this session)

For investigate_command.py

Keep as-is since investigation sessions intentionally allow flexibility to create tickets in any backend.

Acceptance Criteria

• jira_new_command.py prompt clarifies to use 'daf jira create' for consistency
• git_new_command.py prompt clarifies to use 'daf git create' for consistency
• Prompts don't create ambiguity about which command to use
• investigate_command.py references can remain (they're intentionally flexible)
• Documentation in daf-workflow skill is consistent
• Test ticket creation sessions to verify prompts are clear

Notes

Alternative approach: Remove mention of the command entirely:

3. Create a detailed JIRA {issue_type} based on your analysis

This assumes the AI knows to use the appropriate command, but might be less explicit.

Recommendation: Keep the command name but add "(same backend as this session)" to reinforce consistency.

[itdove]

Pull request created: #354

[itdove]

✅ Session Complete

Project: devaiflow
Goal: #351: Fix confusing instructions in ticket creation session prompts
Time Spent:
0h 9m total

• dvernier: 0h 8m
• unknown: 0h 0m
  Branch: 351

Summary

I've successfully fixed the confusing instructions in the ticket creation session prompts. Here's what was changed:

Changes Made

1. devflow/cli/commands/jira_new_command.py (line 878)

• Before: "3. Create a detailed JIRA {issue_type} using the 'daf jira create' command"
• After: "3. Create the JIRA {issue_type} using 'daf jira create' (this session uses JIRA backend)"

2. devflow/cli/commands/git_new_command.py (line 879)

• Before: "3. Create a detailed GitHub/GitLab issue{...} using the 'daf git create' command"
• After: "3. Create the GitHub/GitLab issue{...} using 'daf git create' (this session uses GitHub/GitLab backend)"

3. devflow/cli/commands/investigate_command.py

• No changes needed - Intentionally allows flexibility for both JIRA and GitHub/GitLab

4. daf-workflow skill

• No changes needed - Already consistent and clear

Improvements

The updated prompts now:

• ✅ Remove ambiguity by explicitly stating which backend the session uses
• ✅ Simplify the language ("Create the" instead of "Create a detailed")
• ✅ Add context in parentheses to reinforce consistency
• ✅ Don't suggest switching between issue tracker backends

Testing

All 3,629 tests passed (65 skipped), confirming the changes don't break existing functionality.

The prompts are now clearer and explicitly guide the AI to use the same command type that started the session (daf jira new → daf jira create, daf git new → daf git create).

Generated by DevAIFlow