feat(prompts): add dt-method-next routing prompt

[ofimbres]

Pull Request

Description

Implements DT method routing prompt that analyzes Design Thinking coaching state and routes to appropriate methods with transition validation.

This PR adds a new /dt-method-next prompt that:

• Analyzes current DT project coaching state from .copilot-tracking/dt/{project-slug}/coaching-state.md
• Recommends next method based on completion indicators and sequencing rules
• Validates transitions at space boundaries (Problem→Solution, Solution→Implementation)
• Handles edge cases: no project, all methods complete, iteration loops
• Delegates to dt-coach agent with proper state updates

Related Issue(s)

Fixes #572

Type of Change

AI Artifacts:

• Reviewed contribution with prompt-builder agent and addressed all feedback
• Copilot prompt (.github/prompts/*.prompt.md)

Sample Prompts (for AI Artifact Contributions)

User Request:

/dt-method-next

or

/dt-method-next project-slug=my-dt-project

Execution Flow:

1. Locate project directory by deriving project-slug from input, open files, or conversation context
2. Read coaching state YAML frontmatter from .copilot-tracking/dt/{project-slug}/coaching-state.md
3. Scan project directory for artifact subdirectories matching method-{NN}-*/ patterns
4. Assess method completeness against exit signals from dt-method-sequencing.instructions.md
5. Apply progression logic (forward, backward iteration, or lateral transitions)
6. Present project status summary with suggested next method and rationale
7. Wait for user confirmation
8. Delegate to dt-coach agent to transition coaching into target method

Output Artifacts:

Console output showing:

• Project name and slug
• Current method number, name, and phase
• Progress (N of 9 methods completed)
• Recent work summary
• Key artifacts from current method
• Suggested next method with rationale
• Readiness check for space boundary transitions
• User choice prompt

Success Indicators:

• ✅ Prompt correctly identifies project from context or input
• ✅ Method recommendation aligns with completion indicators
• ✅ Space boundary transitions validate readiness signals
• ✅ Edge cases handled with appropriate user guidance
• ✅ Coaching state updated after confirmation
• ✅ dt-coach loads target method instructions

Testing

Validation Results

All automated checks pass:

• ✅ Markdown linting: npm run lint:md (no errors for dt-method-next.prompt.md)
• ✅ Frontmatter validation: npm run lint:frontmatter (valid schema)
• ✅ Collection metadata: npm run plugin:validate (design-thinking: 35 items, 0 errors)
• ✅ Plugin generation: Commands generated successfully

Manual Testing

Verified against implementation plan:

• ✅ Frontmatter includes description, agent: 'dt-coach', and argument-hint
• ✅ Input variable ${input:project-slug} documented with inference behavior
• ✅ Method state assessment reads artifact directories and evaluates completeness
• ✅ Progression logic covers all 9 methods with correct sequencing
• ✅ Output format provides clear project status summary and recommendation
• ✅ Edge cases handled: no project, all complete, iteration loops
• ✅ Delegates to dt-coach after recommendation
• ✅ Prompt-builder compliance verified

Checklist

Required Checks

• Documentation is updated (if applicable)
• Files follow existing naming conventions
• Changes are backwards compatible (if applicable)
• Tests added for new functionality (if applicable)

AI Artifact Contributions

• Used /prompt-analyze to review contribution
• Addressed all feedback from prompt-builder review
• Verified contribution follows common standards and type-specific requirements

Required Automated Checks

The following validation commands must pass before merging:

• Markdown linting: npm run lint:md
• Spell checking: npm run spell-check
• Frontmatter validation: npm run lint:frontmatter
• Skill structure validation: npm run validate:skills
• Link validation: npm run lint:md-links
• PowerShell analysis: npm run lint:ps

Security Considerations

• This PR does not contain any sensitive or NDA information
• Any new dependencies have been reviewed for security issues
• Security-related scripts follow the principle of least privilege

Additional Notes

Review Findings Summary

Implementation review completed with overall status: ⚠️ Needs Minor Rework (documentation gaps only)

Findings:

• 0 Critical
• 2 Major (documentation-related, not functional)
• 1 Minor

Major Findings (Non-blocking):

1. File naming deviation: Plan specified dt-route-method.prompt.md but implementation uses dt-method-next.prompt.md (better name, more user-friendly)
2. Missing changes log: Expected at .copilot-tracking/changes/2026-02-20/dt-method-routing-changes.md

All functional requirements met. All validation passes. The implementation successfully delivers comprehensive DT method routing with state-aware validation, edge case handling, and proper integration.

Review Log: .copilot-tracking/reviews/2026-02-20/dt-method-routing-review.md

Files Changed

• Added: .github/prompts/design-thinking/dt-method-next.prompt.md - Main routing prompt
• Modified: .github/agents/design-thinking/dt-coach.agent.md - Added handoff entry
• Modified: collections/design-thinking.collection.yml - Added prompt reference
• Modified: collections/design-thinking.collection.md - Documented new prompt
• Modified: collections/hve-core-all.collection.yml - Added to all-in-one collection
• Generated: plugins/design-thinking/commands/dt-method-next.md - Plugin command output
• Generated: plugins/hve-core-all/commands/dt-method-next.md - Plugin command output
• Generated: Various plugin README.md files updated with new command