project-task-migrations_skill

Overview

This skill manages project state using append-only, time-stamped Markdown migration files under /project/. It enforces a context-first workflow, explicit confirmation gates, and immutable history so teams keep an auditable, reversible record of decisions. Use it to coordinate multi-epic work, preserve rationale, and maintain rollback visibility.

How this skill works

The skill reads the latest /project/*.md file to load current epics, tasks, and constraints, then summarizes context before drafting a new migration. Each migration is a new YYYY-MM-DD-topic.md file appended to the project directory. Changes are only applied after an explicit user confirmation step, preserving a forward-only, auditable history.

When to use it

• Managing multi-epic initiatives with interdependent workstreams
• Coordinating cross-functional or distributed teams asynchronously
• Projects with compliance or audit trail requirements
• Work requiring clear rollback visibility and decision provenance
• Situations where team alignment and single-source-of-truth are needed

Best practices

• Always load and review the most recent /project/*.md before proposing changes
• Write concise, time-stamped migration filenames using YYYY-MM-DD-topic.md
• Summarize current epics, open tasks, and blockers in the context section before any change
• Keep migration entries append-only; never modify past files—create a compensating migration instead
• Require an explicit confirmation step and record who approved the migration

Example use cases

• Record requirement and scope changes for a multi-epic product launch with immutable history
• Document cross-team API contract decisions, including rationale and rollback steps
• Maintain audit-ready change logs in regulated environments (finance, healthcare, government)
• Coordinate asynchronous work across time zones by providing a single source of truth and decision trail
• Create rollback migration to revert a deployment change and document the reason and outcome