migration-tracker

Document and track migration status from Portfolio Buddy to Futures Arena.

1|Updated Nov 14, 2025
One-click install
npx skills add https://github.com/5MinFutures/futures-arena --skill migration-tracker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migration-tracker
Source: https://github.com/5MinFutures/futures-arena/tree/main/.claude/skills/migration-tracker
Command: npx skills add https://github.com/5MinFutures/futures-arena --skill migration-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a centralized context and tracking mechanism for migrating from the old Portfolio Buddy app to the new Futures Arena platform, helping teams understand why changes exist, what has been migrated, and what remains to be migrated.

Core Features & Use Cases

  • Migration status dashboards: summarize completed, in-progress, and not-started migration items.
  • Feature parity analysis: document the mapping between old and new features, including known issues and gaps.
  • Auditable changelogs: record commits, touched files, and rationale to support debugging, onboarding, and retrospectives.

Quick Start

Open the migration-tracker skill and review the Migration Status section to see the current progress, milestones, and known issues.

Frequently Asked Questions about migration-tracker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track migration progress and feature parity between apps?

Track migration progress by documenting completed, in-progress, and not-started items alongside feature parity mapping. This provides a clear audit trail of why changes exist and what remains to be migrated for developers.

What is the best way to maintain an audit trail for an ongoing software migration?

Maintain an audit trail by recording commits, touched files, scope, status, and decision rationales. This specifies mapping between old and new features to support debugging, onboarding, and retrospectives during migration.

How does feature parity analysis work when moving to a new platform?

Feature parity analysis works by documenting the mapping between old and new features, including known issues and gaps. It specifies scope and rationale to enable quick search and easy traceability for developers.

Can I use a migration tracker for bug fixes and migration planning?

Yes, a migration tracker applies to bug fixes, feature parity checks, migration planning, and decision rationales. It provides centralized context to understand what has been migrated and what remains.

Why do I need to document decision rationales during an app migration?

Document decision rationales to provide a clear audit trail for developers. This centralized context helps teams understand why changes exist, enabling quick search and easy traceability for future debugging and onboarding.