platform-rewrite

Enforce a six-phase architecture decision process for CloudNow projects.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/acedergren/oci-self-service-portal --skill platform-rewrite
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: platform-rewrite
Source: https://github.com/acedergren/oci-self-service-portal/tree/main/.agents/skills/migrate/platform-rewrite
Command: npx skills add https://github.com/acedergren/oci-self-service-portal --skill platform-rewrite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enterprise teams often struggle with ambiguous architecture decisions and scope creep on large Cloud initiatives. Platform platform rewrite with a six-phase, hard-gated workflow provides a disciplined, evidence-based method to audit the current codebase, research ecosystem options, design target architectures, apply governance standards, score decisions (ADR), and deliver a concrete 90-day execution plan.

Core Features & Use Cases

  • Structured six-phase process: P1 through P6 with mandatory gates to prevent scope drift.
  • Evidence-driven decisions: Every major claim requires repository and external sources citations.
  • Parallel subagent execution: Supports subagents running in parallel to accelerate audit, research, and design tasks.
  • ** ADR scoring and governance**: Architecture Decision Records with deterministic acceptance criteria and gating.
  • Real-world use case: For a CloudNow migration, produce an actionable rewrite plan including milestones, risks, and mitigations.

Quick Start

Run the platform-rewrite workflow to begin the six-phase architecture decision process for CloudNow.

Frequently Asked Questions about platform-rewrite

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

FAQPage Schema
How do I plan a cloud architecture rewrite without scope creep?

A gated, six-phase architecture rewrite workflow prevents scope creep by enforcing mandatory phase-gates between each stage. It requires traceable evidence and deterministic acceptance criteria to progress, ensuring disciplined cloud migration planning.

What is a phase-gate process for architecture decisions?

A phase-gate process for architecture decisions enforces mandatory checkpoints across six distinct phases of a rewrite. It requires documented gating rules and deterministic acceptance criteria to be met before allowing progression to the next project phase.

How do I create an Architecture Decision Record with evidence?

Create an evidence-backed ADR by applying governance scoring and requiring traceable citations from repository and external sources. This ensures every major architecture claim is validated before entering the final 90-day execution plan.

Can I use parallel subagents to accelerate a codebase audit?

Yes, the architecture rewrite workflow supports parallel subagent execution to accelerate codebase audits, external research, and target design tasks. This enables concurrent evidence gathering across the six phases to speed up decision-making.

What deliverables should I expect from a CloudNow migration planning workflow?

Expect an evidence-backed Architecture Decision Record (ADR) and a concrete 90-day execution plan as final deliverables. The plan includes actionable milestones, identified risks, and mitigations tailored for a CloudNow migration project.