Unify task workflows and rename productionalize command

[jsegov]

Summary

• Rename /productionalize to /production-readiness-review for clearer naming
• Unify task output format: production-reporter now generates TASKS.md instead of fix-prompts.md
• Enhance /implement-next-task to support both feature planning (TASK-XXX) and production readiness (FINDING-XXX) workflows
• Add MIT license
• Rename plugin to "ShipSpec Claude Code Plugin" in README

Test plan

• Run /production-readiness-review and verify it generates TASKS.md with FINDING-XXX format
• Run /implement-next-task on a production readiness context and verify workflow detection
• Run /implement-next-task on a feature planning context and verify it still works
• Verify argument validation shows helpful error when no argument provided

🤖 Generated with Claude Code

---

Note

Production readiness workflow changes

• Renames command to /production-readiness-review and updates output to generate production-report.md plus unified TASKS.md (replaces fix-prompts.md)
• Updates production-reporter to document findings in production-report.md and emit structured remediation tasks in TASKS.md

Task execution improvements

• Enhances /implement-next-task to detect workflow type (feature vs production), handle FINDING-XXX and TASK-XXX, add argument validation, dependency handling, and edge-case checks

Docs and housekeeping

• Renames plugin to "ShipSpec Claude Code Plugin" in README.md
• Adds LICENSE (MIT)

^{Written by Cursor Bugbot for commit 382633d. This will update automatically on new commits. Configure here.}

[claude]

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

[cursor]

Workflow detection lacks inline priority for overlapping artifacts

Medium Severity

The workflow detection rules at lines 49-51 are written as independent conditions without handling the overlap case where both feature planning artifacts (PRD.md/SDD.md) and production readiness artifacts (production-report.md) exist in the same directory. The bash script on lines 45-46 outputs both FEATURE_PLANNING and PRODUCTION_READINESS when all files exist. The priority rule at lines 231-232 clarifies that production readiness should take precedence, but this edge case handling is separated from the main detection logic, which could cause an agent to select the wrong workflow type, resulting in incorrect task ID format (TASK-XXX vs FINDING-XXX).

Additional Locations (1)

• commands/implement-next-task.md#L230-L232