spec-workflow-mcp（spec 工作流 MCP）

Spec Workflow MCP

Spec Workflow MCP v2.0.0 — a productivity toolkit for spec-driven development workflows served via the Model Context Protocol (MCP). Manage tasks, plan sprints, track progress, review deliverables, set reminders, prioritize work, and run weekly reviews — all from the command line with timestamped log entries.

Commands

The script (scripts/script.sh) exposes the following commands via a case dispatcher:

How Each Entry Command Works

1. If called without arguments, it tails the last 20 lines of <command>.log.
2. If called with arguments, it:

- Timestamps the input (YYYY-MM-DD HH:MM|<input>) - Appends it to $DATA_DIR/<command>.log - Prints confirmation with the current total count - Logs the action to history.log

Data Storage

All data is stored as plain-text log files under:

~/.local/share/spec-workflow-mcp/
├── add.log
├── plan.log
├── track.log
├── review.log
├── streak.log
├── remind.log
├── prioritize.log
├── archive.log
├── tag.log
├── timeline.log
├── report.log
├── weekly-review.log
└── history.log          # unified activity log

Each log line uses pipe-delimited format: YYYY-MM-DD HH:MM|<value>

The history.log uses: MM-DD HH:MM <command>: <value>

Requirements

• Bash 4.0+ (uses local variables, set -euo pipefail)
• coreutils: date, wc, du, tail, cat, basename, grep, sed
• No external dependencies, API keys, or network access required
• Works on Linux and macOS

When to Use

1. Sprint planning — use plan to record iteration goals, then track to log progress against them throughout the sprint
2. Task management — use add to capture new specs or tasks, prioritize to rank them, and archive when complete
3. Daily standups — use streak to maintain consistency tracking and recent to review what happened yesterday
4. Code/spec reviews — use review to log review notes and decisions for future reference
5. Weekly retrospectives — use weekly-review to capture weekly summaries, then export to generate reports for stakeholders

Examples

Add a task and plan a sprint

# Add a new spec
bash scripts/script.sh add "API rate limiting — sliding window implementation"

# Plan the sprint
bash scripts/script.sh plan "Sprint 8: rate limiter, caching layer, monitoring"

Track progress and review

# Track completion
bash scripts/script.sh track "rate limiter: Redis backend done, unit tests passing"

# Log a review
bash scripts/script.sh review "rate limiter PR #87: approved, added integration tests"

Set reminders and manage priorities

# Set a reminder
bash scripts/script.sh remind "demo prep for Friday stakeholder meeting"

# Prioritize
bash scripts/script.sh prioritize "P1: cache invalidation edge case in multi-region"

Weekly review and export

# Record weekly summary
bash scripts/script.sh weekly-review "shipped rate limiter, started caching layer, blocked on Redis cluster config"

# Export all data as CSV
bash scripts/script.sh export csv

Search and view timeline

# Find all entries mentioning "cache"
bash scripts/script.sh search "cache"

# Log a milestone
bash scripts/script.sh timeline "v2.1 release candidate tagged"

# View overall statistics
bash scripts/script.sh stats

Configuration

Set the DATA_DIR variable (or modify it in the script) to change the storage directory. Default: ~/.local/share/spec-workflow-mcp/

Output

All commands print to stdout. Redirect to a file as needed:

bash scripts/script.sh weekly-review > retro-notes.txt

Powered by BytesAgain | bytesagain.com | hello@bytesagain.com