Template

Files

lmiranda 3561025dfc feat(projman): add visual output requirements to agents and commands

Add Visual Output sections to all projman files:
- 4 agent files with phase-specific headers (PLANNING, EXECUTION, CLOSING)
- 16 command files with appropriate headers

Headers use double-line box characters for projman branding:
- Planning phase: TARGET PLANNING
- Execution phase: LIGHTNING EXECUTION (+ progress block for orchestrator)
- Closing phase: FLAG CLOSING
- Setup commands: GEAR SETUP

Closes #273, #274

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-01-28 17:10:49 -05:00

5.5 KiB

Raw Blame History

description

description
Generate Mermaid diagram of sprint issues with dependencies and status

Sprint Diagram

This command generates a visual Mermaid diagram showing the current sprint's issues, their dependencies, and execution flow.

What This Command Does

Fetch Sprint Issues - Gets all issues for the current sprint milestone
Fetch Dependencies - Retrieves dependency relationships between issues
Generate Mermaid Syntax - Creates flowchart showing issue flow
Apply Status Styling - Colors nodes based on issue state (open/closed/in-progress)
Show Execution Order - Visualizes parallel batches and critical path

Usage

/sprint-diagram
/sprint-diagram --milestone "Sprint 4"

MCP Tools Used

Issue Tools:

list_issues(state="all") - Fetch all sprint issues
list_milestones() - Find current sprint milestone

Dependency Tools:

list_issue_dependencies(issue_number) - Get dependencies for each issue
get_execution_order(issue_numbers) - Get parallel execution batches

Implementation Steps

Get Current Milestone:

milestones = list_milestones(state="open")
current_sprint = milestones[0]  # Most recent open milestone

Fetch Sprint Issues:

issues = list_issues(state="all", milestone=current_sprint.title)

Fetch Dependencies for Each Issue:

dependencies = {}
for issue in issues:
    deps = list_issue_dependencies(issue.number)
    dependencies[issue.number] = deps

Generate Mermaid Diagram:

flowchart TD
    subgraph Sprint["Sprint 4 - Commands"]
        241["#241: sprint-diagram"]
        242["#242: confidence threshold"]
        243["#243: pr-diff"]

        241 --> 242
        242 --> 243
    end

    classDef completed fill:#90EE90,stroke:#228B22
    classDef inProgress fill:#FFD700,stroke:#DAA520
    classDef open fill:#ADD8E6,stroke:#4682B4
    classDef blocked fill:#FFB6C1,stroke:#DC143C

    class 241 completed
    class 242 inProgress
    class 243 open

Expected Output

Sprint Diagram: Sprint 4 - Commands
===================================

```mermaid
flowchart TD
    subgraph batch1["Batch 1 - No Dependencies"]
        241["#241: sprint-diagram<br/>projman"]
        242["#242: confidence threshold<br/>pr-review"]
        244["#244: data-quality<br/>data-platform"]
        247["#247: chart-export<br/>viz-platform"]
        250["#250: dependency-graph<br/>contract-validator"]
        251["#251: changelog-gen<br/>doc-guardian"]
        254["#254: config-diff<br/>config-maintainer"]
        256["#256: cmdb-topology<br/>cmdb-assistant"]
    end

    subgraph batch2["Batch 2 - After Batch 1"]
        243["#243: pr-diff<br/>pr-review"]
        245["#245: lineage-viz<br/>data-platform"]
        248["#248: color blind<br/>viz-platform"]
        252["#252: doc-coverage<br/>doc-guardian"]
        255["#255: linting<br/>config-maintainer"]
        257["#257: change-audit<br/>cmdb-assistant"]
    end

    subgraph batch3["Batch 3 - Final"]
        246["#246: dbt-test<br/>data-platform"]
        249["#249: responsive<br/>viz-platform"]
        253["#253: stale-docs<br/>doc-guardian"]
        258["#258: IP conflict<br/>cmdb-assistant"]
    end

    batch1 --> batch2
    batch2 --> batch3

    classDef completed fill:#90EE90,stroke:#228B22
    classDef inProgress fill:#FFD700,stroke:#DAA520
    classDef open fill:#ADD8E6,stroke:#4682B4

    class 241,242 completed
    class 243,244 inProgress

Status Legend

Status	Color	Description
Completed	Green	Issue closed
In Progress	Yellow	Currently being worked on
Open	Blue	Ready to start
Blocked	Red	Waiting on dependencies

Diagram Types

Default: Dependency Flow

Shows how issues depend on each other with arrows indicating blockers.

Batch View (--batch)

Groups issues by execution batch for parallel work visualization.

Plugin View (--by-plugin)

Groups issues by plugin for component-level overview.

When to Use

Sprint Planning: Visualize scope and dependencies
Daily Standups: Show progress at a glance
Documentation: Include in wiki pages
Stakeholder Updates: Visual progress reports

Integration

The generated Mermaid diagram can be:

Pasted into GitHub/Gitea issues
Rendered in wiki pages
Included in PRs for context
Used in sprint retrospectives

Example

User: /sprint-diagram

Generating sprint diagram...

Milestone: Sprint 4 - Commands (18 issues)
Fetching dependencies...
Building diagram...

```mermaid
flowchart LR
    241[sprint-diagram] --> |enables| 242[confidence]
    242 --> 243[pr-diff]

    style 241 fill:#90EE90
    style 242 fill:#ADD8E6
    style 243 fill:#ADD8E6

Open: 16 | In Progress: 1 | Completed: 1


## Visual Output

When executing this command, display the plugin header:

╔══════════════════════════════════════════════════════════════════╗ ║ 📋 PROJMAN ║ ║ Sprint Diagram ║ ╚══════════════════════════════════════════════════════════════════╝


Then proceed to generate the diagram.

5.5 KiB Raw Blame History