workflow

Route user intents to appropriate engineering skills across planning, execution, and review.

Updated Mar 12, 2019
One-click install
npx skills add https://github.com/gustavofsantos/dot-files --skill workflow-gustavofsantos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow
Source: https://github.com/gustavofsantos/dot-files/tree/main/skills/workflow
Command: npx skills add https://github.com/gustavofsantos/dot-files --skill workflow-gustavofsantos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Coordinates and routes user intents to the appropriate skills so engineering work can be planned, executed, and reviewed without losing context.

Core Features & Use Cases

  • Central routing: decides which skill to invoke based on user input and session state.
  • Session and context management: maintains continuity across sessions and recalls relevant information.
  • Issue-driven workflow: uses an issue model to track progress through planning, execution, and review.

Quick Start

Describe your issue or request and I will route it to the appropriate skills to begin planning or execution.

Frequently Asked Questions about workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate engineering tasks across planning and review phases without losing session context?

You can orchestrate engineering work by describing your issue or request to a central routing entry point, which evaluates session state and decides which skills to invoke for planning, execution, or review.

What is the best way to manage work continuity across multiple engineering sessions?

Managing work continuity across multiple engineering sessions requires a central router that maintains session context and recalls relevant information, ensuring progress is tracked through an issue-driven model across all phases.

Can I use a single entry point to route different engineering requests to specialized skills?

Yes, a single entry point can route different engineering requests by evaluating user input and session state to decide which specialized skills to invoke for coordinating work across planning, execution, and review.

How does issue-driven workflow track progress through execution and review phases?

Issue-driven workflow tracks progress by using an issue model to coordinate tasks across execution and review phases, routing intents to appropriate skills while maintaining session context throughout the engineering lifecycle.

Do I need specific dependencies to coordinate engineering work across planning and execution?

No specific dependencies are required to coordinate engineering work across planning and execution, as the routing system operates independently using scripts to manage session context and orchestrate tasks.