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:
Command
Description
INLINECODE2
Add a new spec/task entry. Without args, shows the 20 most recent add entries.
INLINECODE3
Record a planning entry (sprint planning, iteration goals). Without args, lists recent plans. |
| track <input> | Track progress on a task or deliverable. Without args, lists recent tracking entries. |
| review <input> | Record a review note (code review, spec review). Without args, lists recent reviews. |
| streak <input> | Log a streak entry (daily consistency tracking). Without args, lists recent streaks. |
| remind <input> | Set a reminder or log a reminder note. Without args, lists recent reminders. |
| prioritize <input> | Record a prioritization decision. Without args, lists recent prioritizations. |
| archive <input> | Archive a completed item. Without args, lists recent archive entries. |
| tag <input> | Tag or categorize an entry. Without args, lists recent tags. |
| timeline <input> | Record a timeline/milestone entry. Without args, lists recent timeline entries. |
| report <input> | Generate or log a report entry. Without args, lists recent reports. |
| weekly-review <input> | Record a weekly review summary. Without args, lists recent weekly reviews. |
| stats | Show summary statistics across all log files (entry counts per type, total, disk usage). |
| export <fmt> | Export all data in json, csv, or txt format to $DATA_DIR/export.<fmt>. |
| search <term> | Search all log files for a term (case-insensitive grep). |
| recent | Show the 20 most recent lines from history.log. |
| status | Health check — shows version, data directory, total entries, disk usage, last activity. |
| help | Display the full help/usage message. |
| version | Print spec-workflow-mcp v2.0.0. |
How Each Entry Command Works
1. If called without arguments, it tails the last 20 lines of <command>.log.
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 INLINECODE30
Data Storage
All data is stored as plain-text log files under:
CODEBLOCK0
Each log line uses pipe-delimited format: INLINECODE31
The history.log uses: INLINECODE33
Requirements
- Bash 4.0+ (uses local variables, set -euo pipefail)
coreutils: date, wc, du, tail, cat, basename, grep, INLINECODE43
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
Task management — use add to capture new specs or tasks, prioritize to rank them, and archive when complete
Daily standups — use streak to maintain consistency tracking and recent to review what happened yesterday
Code/spec reviews — use review to log review notes and decisions for future reference
Weekly retrospectives — use weekly-review to capture weekly summaries, then export to generate reports for stakeholders
Examples
Add a task and plan a sprint
CODEBLOCK1
Track progress and review
CODEBLOCK2
Set reminders and manage priorities
CODEBLOCK3
Weekly review and export
CODEBLOCK4
Search and view timeline
CODEBLOCK5
Configuration
Set the DATA_DIR variable (or modify it in the script) to change the storage directory. Default: INLINECODE55
Output
All commands print to stdout. Redirect to a file as needed:
CODEBLOCK6
Powered by BytesAgain | bytesagain.com | hello@bytesagain.com
