Workflow Commands

Workflow MCP supports seven commands, each for a specific phase of development work.

Command Overview

Command	Purpose	Output Directory	Input Directories	Default DPS
`/research`	Gather information	`projects/research/`	None (fresh start)	4
`/plan`	Design implementation	`projects/plans/`	research, interactions, backlog	1
`/implement`	Execute the plan	`projects/implementations/`	plans, research	1
`/review`	Verify completeness	`projects/reviews/`	research, plans, implementations	3
`/debug`	Diagnose issues	`projects/debug/`	research, plans, implementations	4
`/refactor`	Analyze for improvement	`projects/research/`	.archived/completed, implementations	3
`/archive`	Archive completed work	`projects/.archived/archive-logs/`	research, plans, implementations, reviews	0

All commands support the blocker entry type for logging blocking issues with DPS-aware guidance.

Command Details

/research

Purpose: Gather information, explore options, understand the problem space.

Entry Types: finding (RES), requirement (REQ), blocker (BLK)

Inputs: None (starts fresh)

Outputs: Research findings that inform planning

Next Phase: /plan

Example:

/workflow:research AUTH-MIGRATION
/workflow:research AUTH-MIGRATION dps=5 focus on OAuth patterns

/plan

Purpose: Design the implementation approach based on research.

Entry Types: decision (PLN), directive (DIR), blocker (BLK)

Inputs: Automatically links to latest research, interactions, and backlog files for the topic

Outputs: Implementation plan with tasks

Next Phase: /implement

Example:

/workflow:plan AUTH-MIGRATION
/workflow:plan AUTH-MIGRATION dps=2

/implement

Purpose: Execute the plan, write code, create tests.

Entry Types: task-complete (IMP), user-feedback (UFB), issue (IMP), blocker (BLK)

Inputs: Automatically links to latest plan and research files

Outputs: Completed tasks, changed files

Next Phase: /review

Example:

/workflow:implement AUTH-MIGRATION
/workflow:implement AUTH-MIGRATION dps=2 llm=true

/review

Purpose: Verify implementation against research and plan.

Entry Types: gap with prefixes:

GAP-RP: Research → Plan gaps
GAP-PI: Plan → Implementation gaps

Inputs: Automatically links to research, plan, and implementation files

Outputs: Gap analysis and recommendations

Next Phase: /plan (if gaps found)

Example:

/workflow:review AUTH-MIGRATION

/debug

Purpose: Diagnose and fix issues.

Entry Types: fault (DBG), investigation (DBG), fix (FIX), verification (VER), blocker (BLK)

Inputs: Automatically links to research, plan, and implementation files

Outputs: Root cause analysis, applied fixes

Example:

/workflow:debug AUTH-ISSUE-42
/workflow:debug AUTH-ISSUE-42 dps=5

/refactor

Purpose: Analyze code for potential improvements.

Entry Types: Same as research (RES-REFACTOR prefix)

Inputs: Automatically links to archived completed projects and implementations

Outputs: Refactoring recommendations (feeds into planning)

Next Phase: /plan

Example:

/workflow:refactor AUTH-MODULE

/archive

Purpose: Archive completed work for future reference.

Entry Types: Archive operations (ARC)

Inputs: All project files (research, plans, implementations, reviews)

Outputs: Archived files in .archived/archive-logs/

Example:

/workflow:archive AUTH-MIGRATION

Command Flow

The typical flow is:

research → plan → implement → review
    ↑                           ↓
    └───────── (if gaps) ───────┘

For bugs:

debug → (identify fix) → implement → review

For improvements:

refactor → plan → implement → review