Conversation
Requirement: Integrate comprehensive context gathering and requirement analysis into /make-task-issue command to enable well-structured issue creation from the start. Clarify separation of concerns between /make-task-issue (problem definition) and /plan-issue (implementation planning) to eliminate duplication and improve workflow efficiency. Implementation: - Added editor-based user input collection workflow with required/optional sections (Context, Requirement, Solution, Constraints, Test Plan) - Added AI context gathering stage using Read/Glob/Grep tools to enhance user input with codebase insights - Added auto-generated issue title based on requirement analysis - Changed from template-based to structured body creation with --body flag - Updated plan-issue.md to focus on implementation steps from well-structured issues - Added separation of concerns documentation in both commands - Added required tools (Read, Glob, Grep, Write) to make-task-issue frontmatter 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Requirement: Each issue type (feat, fix, doc, test, perf, refactor) has unique characteristics that don't fit a one-size-fits-all template structure. Generic sections like "Solution" and "Test Plan" are inappropriate for documentation and testing issues. Implementation: - Customized templates for type-specific needs: - doc: Changed "Solution" to "Content Outline", "Test Plan" to "Verification" - test: Changed "Solution" to "Test Scope", "Test Plan" to "Verification" - perf, refactor: Changed "Test Plan" to "Verification" - fix: Added bug-specific guidance in comments - feat, config, agent: Kept standard structure (Context, Requirement, Solution, Test Plan) - Updated make-task-issue.md to document type-specific sections: - Added type-to-section mapping table - Added examples for feat, doc, and test types - Updated workflow to handle type-specific section names - Updated issue body generation with type-specific structures 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
p-iknow
force-pushed
the
i16-agent/enhance-make-task-issue-with-planning
branch
from
1531103 to
72b9f9b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requirement
Resolves #16
Integrate the interactive planning workflow from
/plan-issueinto/make-task-issueto enable comprehensive issue creation with structured context gathering, requirement definition, solution design, and test planning. Standardize all non-bug issue templates to support this new workflow and clarify separation of concerns between the two commands.Implementation
Agent Command Enhancement
/make-task-issuecommand:--bodyflag/plan-issuecommand:/make-task-issue/make-task-issue: Problem definition (Context, Requirement, Solution, Test Plan)/plan-issue: Implementation planning (breaking down into actionable steps)Template Standardization
Updated 8 issue templates with unified structure:
feat.md,fix.md,doc.md,config.md,refactor.md,agent.md,test.md,perf.mdbug.mdunchanged (serves different purpose for bug reporting)Test
/make-task-issuecommand documentation is complete and clearbug.mdtemplate is unchanged/plan-issuedocumentation clarifies separation of concernsHuman Check
🤖 Generated with Claude Code