ask-matt

Route development tasks by assessing your current project phase and intent, then directing the work to the appropriate specialized skill unit. This workflow routing mechanism bridges ideation, triage, architectural design, and implementation while maintaining consistent context across sessions.

Maintaining context across multi-session engineering efforts requires using specific handoff mechanisms to bridge session limits. Context management ensures process adherence and prevents cognitive overload when transitioning between different development workflows over time.

Determining which engineering process to start involves mapping your current situation to the appropriate agent-driven workflow. If you are unsure whether to begin a new feature, triage bugs, or perform architectural improvements, workflow routing evaluates your project phase to recommend the correct path.

Workflow routing supports both bug triage and architectural design by acting as a central router for development and maintenance workflows. It maps your specific intent to the correct specialized skill, ensuring proper process adherence for each distinct task type.

Use a central routing skill for navigation when you face cognitive overload or process ambiguity in your repository. It is necessary when transitioning between ideation, triage, design, and implementation workflows requires consistent context maintenance across multiple sessions.

Ask-matt manages transitions between ideation and implementation by routing development tasks to specialized skill units based on the current project phase. It ensures consistent context maintenance and process adherence throughout the entire multi-session engineering effort.