replace-strategy

Measures a legacy application and plans its behavior-preserving replacement strategy.

Updated Jul 24, 2026
One-click install
npx skills add https://github.com/shoji9x9/portfolio --skill replace-strategy-shoji9x9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: replace-strategy
Source: https://github.com/shoji9x9/portfolio/tree/main/.agents/skills/replace-strategy
Command: npx skills add https://github.com/shoji9x9/portfolio --skill replace-strategy-shoji9x9

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Replacing an application without changing its specification requires evidence-based decisions, not guesswork. This Skill acts as the entry point for a behavior-preserving replacement: it measures the current application (semantics, DB restore capability, side effects, file I/O reachability), derives a replacement strategy from measured values, decomposes the app into features, and dispatches work to sister skills (golden-dataset / parity-suite / parity-replace / parity-diff). It never implements code itself and stops when measurement is impossible. ## Core Features & Use Cases - setup mode: Checks dependencies (issue-create, browser-test, chrome-devtools MCP), runs an interactive project setup, measures the current app with a role probe script, records a strategy, builds a feature inventory, and decides shared package dependencies. - issues mode: Selects unfiled features from the inventory and files GitHub Issues via the issue-create skill, with an explicit approval gate before any external side effect. - status mode: Derives current progress and unverified areas from GitHub Issues and in-repository artifacts without holding its own state. - Use Case: You want to migrate a legacy order-management app to a new TypeScript stack. Run setup to measure the current app, get a parity-test strategy and feature inventory, then file per-feature Issues that downstream skills implement and verify with deterministic diffing. ## Quick Start Ask the AI to run replace-strategy setup to measure the current application and produce a replacement strategy and feature inventory.

Frequently Asked Questions about replace-strategy

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

FAQPage Schema
How do I plan a legacy application replacement without changing its behavior?▼

Run replace-strategy setup to measure the current application first: role-based semantics, DB restore capability, code availability, side effects, and file I/O reachability. The skill then proposes a parity-suite strategy and feature inventory for your approval, and refuses to produce a strategy from guesses.

What are the setup, issues, and status modes in replace-strategy?▼

setup runs once to measure the app, record strategy, and build the feature inventory. issues files GitHub Issues for selected features via the issue-create skill after explicit approval. status derives current progress and unverified gaps from Issues and repository artifacts each time it runs.

What tools and prerequisites does replace-strategy require?▼

It requires the gh GitHub CLI, git, the issue-create and browser-test skills, and chrome-devtools MCP for semantic measurement. Without a working MCP it cannot measure the current app, so it shows installation steps and stops rather than continuing.

Does replace-strategy implement the new application code?▼

No. It only measures, decides strategy, decomposes features, and dispatches work to sister skills: golden-dataset, parity-suite, parity-replace, and parity-diff. Implementation happens in those downstream skills after Issues are filed.

Why does replace-strategy stop instead of estimating when measurement fails?▼

Its core discipline is that strategy decisions depend on measured values, so unmeasurable areas are marked as unmeasured and the skill halts before strategy. This prevents guesses from contaminating the parity baseline that downstream verification relies on.

Can replace-strategy handle file outputs like CSV, Excel, and PDF?▼

Yes, it measures file I/O reachability during setup and records how outputs are captured. CSV and text are compared byte-for-byte, while xlsx and PDF are compared via extracted values and structure because their bytes contain volatile metadata.