rewrite

Extract business logic and map dependencies for a governed rewrite workflow.

Updated Dec 17, 2024
One-click install
npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill rewrite-laf-us
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rewrite
Source: https://github.com/LAF-US/IDAHO-VAULT/tree/main/.ghcp-appmod/skills/rewrite
Command: npx skills add https://github.com/LAF-US/IDAHO-VAULT --skill rewrite-laf-us

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rewrite-mode guidelines solve the challenge of migrating legacy business logic to a modern target stack by providing a structured, governance-aligned blueprint.

Core Features & Use Cases

  • Workflow integration across Analysis, Scaffolding, Implementation, and Verification to support end-to-end migration projects.
  • Risk mitigation and governance adherence through vault standards (VAULT-METADATA-STANDARD, VAULT-TEMPLATES) to ensure traceability and consistency.
  • Use Case: a team migrating a monolith can follow the framework to inventory logic, scaffold a new project, implement in the target stack, and verify functional equivalence.

Quick Start

Begin by reading SKILL.md for the rewrite workflow, complete the inventory checklist, and plan the target scaffolding steps.

Frequently Asked Questions about rewrite

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

FAQPage Schema
How do I extract business logic from a legacy application for a migration rewrite?

To extract business logic for a rewrite, identify and inventory all logic from the source application to enable a clean migration. This ensures complete inventory and external dependency mapping before target scaffolding.

What is the best way to structure a monolith migration to a modern stack?

A monolith migration requires a structured workflow across analysis, scaffolding, implementation, and verification. Applying this governance-aligned blueprint minimizes risk and ensures functional equivalence in the target stack.

How does scaffolding work during a business logic rewrite?

Scaffolding during a rewrite involves planning target project structures after completing a full logic inventory. It follows governance standards to ensure traceability and consistency before implementation begins.

Can I verify functional equivalence after migrating business logic to a new target stack?

Yes, functional equivalence is verified during the verification phase of the migration workflow. This step ensures the rewritten business logic operates correctly in the target stack after implementation.

Do I need vault standards to maintain governance during a software engineering rewrite?

Yes, adhering to vault standards like VAULT-METADATA-STANDARD and VAULT-TEMPLATES is required throughout the rewrite process. This ensures traceability, risk mitigation, and consistency across the migration workflow.

When should I not use a rewrite-mode migration for my application?

Rewrite-mode migration is not ideal if you cannot inventory all source business logic or map external dependencies. The framework relies on complete extraction to minimize migration risk and ensure a clean rewrite.