PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
Assess feasibility and effort of rewriting the application in a different language, framework, or architecture.
Install Rewrite Assessment
$ npx skills add EmeaAppGbb/spec2cloud --skill rewrite-assessment -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install EmeaAppGbb/spec2cloud rewrite-assessment --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/rewrite-assessment .claude/skills/rewrite-assessment && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "rewrite-assessment" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/rewrite-assessment into .claude/skills/rewrite-assessment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rewrite-assessment", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/rewrite-assessmentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add EmeaAppGbb/spec2cloud --skill rewrite-assessment -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install EmeaAppGbb/spec2cloud rewrite-assessment --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/rewrite-assessment .agents/skills/rewrite-assessment && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "rewrite-assessment" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/rewrite-assessment into .agents/skills/rewrite-assessment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rewrite-assessment", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add EmeaAppGbb/spec2cloud --skill rewrite-assessment -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install EmeaAppGbb/spec2cloud rewrite-assessment --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/rewrite-assessment .cursor/skills/rewrite-assessment && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "rewrite-assessment" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/rewrite-assessment into .cursor/skills/rewrite-assessment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rewrite-assessment", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/EmeaAppGbb/spec2cloud.git --path .github/skills/rewrite-assessment--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add EmeaAppGbb/spec2cloud --skill rewrite-assessment -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install EmeaAppGbb/spec2cloud rewrite-assessment --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/rewrite-assessment .gemini/skills/rewrite-assessment && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "rewrite-assessment" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/rewrite-assessment into .gemini/skills/rewrite-assessment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rewrite-assessment", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install EmeaAppGbb/spec2cloud rewrite-assessmentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add EmeaAppGbb/spec2cloud --skill rewrite-assessment -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/rewrite-assessment .github/skills/rewrite-assessment && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "rewrite-assessment" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/rewrite-assessment into .github/skills/rewrite-assessment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rewrite-assessment", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add EmeaAppGbb/spec2cloud --skill rewrite-assessment -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install EmeaAppGbb/spec2cloud rewrite-assessment --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/rewrite-assessment .opencode/skills/rewrite-assessment && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "rewrite-assessment" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/rewrite-assessment into .opencode/skills/rewrite-assessment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rewrite-assessment", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
rewrite-assessment- GitHub stars
- 100
- Token cost
- ~2k tokens
- SKILL.md length
- 760 words
- Files
- 1
- Skills in repo
- 38
- Repo updated
- First seen
- Licence
- MIT
At a glance
Assess feasibility and effort of rewriting the application in a different language, framework, or architecture.
- Works in 6 steps: Current Codebase Complexity Analysis → Feature Preservation Map → Translation Feasibility → …
- Tasks that involve Architecture decision records
- SKILL.md covers Role, Inputs, Process and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Rewrite Assessment is an agent skill from EmeaAppGbb/spec2cloud. Assess feasibility and effort of rewriting the application in a different language, framework, or architecture. Compare current stack against target stack. Produce ADRs for rewrite vs modernize decision.
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Architecture decision records. The licence is MIT.
When your agent uses it
- Tasks that involve Architecture decision records
Example prompts
- “/rewrite-assessment”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 8e76618. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Rewrite Assessment loads about 2k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 760 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from EmeaAppGbb/spec2cloud at commit 8e76618, republished under its MIT licence (© EmeaAppGbb). 760 words, ~2,028 tokens.
Download SKILL.mdSave it as
.claude/skills/rewrite-assessment/SKILL.md (or your agent's skills folder).- name
- rewrite-assessment
- description
- Assess feasibility and effort of rewriting the application in a different language, framework, or architecture. Compare current stack against target stack. Produce ADRs for rewrite vs modernize decision.
Role
You are a rewrite feasibility analyst. Your job is to objectively evaluate whether rewriting an application (fully or partially) is justified compared to incremental modernization. You produce evidence-based analysis — not advocacy for either approach.
You are activated when the user selects the rewrite path. You do not run automatically.
Inputs
specs/docs/technology/*— Current technology inventoryspecs/docs/architecture/*— Current architecture documentationspecs/docs/dependencies/*— Dependency manifestsspecs/docs/features/*— Feature inventory (if available from extraction)- User-specified target stack — The language, framework, or architecture the user is considering rewriting to. Ask if not provided.
Process
Follow this sequence. Each step informs the next.
Step 1 — Current Codebase Complexity Analysis
Quantify the scope of what exists:
- Lines of code by language (excluding generated code, vendor, tests)
- Component count: Distinct modules, services, packages, or bounded contexts
- Integration points: External APIs, databases, message queues, file systems, third-party services
- Data model complexity: Number of entities, relationships, migration history
- Configuration surface: Environment variables, feature flags, config files
- Build complexity: Build steps, custom tooling, code generation
Step 2 — Feature Preservation Map
Identify everything the rewrite must preserve:
- Core features: Business logic that must work identically
- Edge cases: Documented (or discovered) special handling
- Integration contracts: API schemas, message formats, data formats that external systems depend on
- Non-functional requirements: Performance SLAs, compliance requirements, accessibility standards
- User-facing behavior: UI flows, error messages, notification patterns
Classify each feature area as:
- Must preserve: Breaking change if missing
- Should preserve: Users expect it but could accept temporary gap
- Can reimagine: Opportunity to improve during rewrite
Step 3 — Translation Feasibility
For each component, assess automated vs manual translation:
| Component Type | Auto-translatable? | Notes |
|---|---|---|
| Data models | Often yes | Schema migration tools exist |
| REST APIs | Partially | OpenAPI spec helps, logic doesn't |
| Business logic | Rarely | Manual rewrite usually required |
| UI components | Sometimes | Depends on framework similarity |
| Infrastructure | Yes | IaC is generally portable |
| Tests | Rarely | Must rewrite, but specs carry over |
Produce a component-by-component assessment.
Step 4 — Effort Estimation
For each feature area, estimate rewrite effort:
- T-shirt size: S (days), M (weeks), L (months), XL (quarters)
- Confidence level: High (clear scope), Medium (some unknowns), Low (significant unknowns)
- Risk factors: What could make this harder than estimated
Sum to produce a total rewrite effort range (optimistic / realistic / pessimistic).
Step 5 — Rewrite vs Modernize Comparison
Build a side-by-side comparison:
| Dimension | Modernize | Rewrite |
|---|---|---|
| Estimated effort | ||
| Time to first value | ||
| Risk level | ||
| Team skill requirement | ||
| Feature parity timeline | ||
| Long-term maintenance | ||
| Technical debt carried |
Step 6 — Risk Analysis
Identify and rate risks specific to the rewrite path:
- Data migration risk: Schema changes, data transformation, rollback capability
- Integration compatibility: Will existing integrations work during/after rewrite?
- Feature parity gap: Period where rewrite lacks features the current system has
- Knowledge loss: Implicit behavior in current code that isn't documented
- Parallel maintenance: Cost of maintaining both systems during transition
- Team ramp-up: If target stack is new to the team
Rate each risk: Low / Medium / High / Critical
Show full SKILL.md (288 more words)Show less
Output Format
Generate specs/assessment/rewrite.md with this structure:
# Rewrite Assessment
## Executive Summary
One-paragraph recommendation with confidence level.
## Current System Profile
- Total LOC: [N] across [N] languages
- Components: [N]
- Integration points: [N]
- Data entities: [N]
- Estimated complexity: [Low/Medium/High/Very High]
## Target Stack
- Language: [X]
- Framework: [X]
- Rationale provided by user: [X]
## Feature Preservation Map
| Feature Area | Classification | Complexity | Notes |
|---|---|---|---|
## Translation Feasibility
| Component | Auto-translatable | Manual Effort | Risk |
|---|---|---|---|
## Effort Comparison
| Dimension | Modernize | Rewrite |
|---|---|---|
## Risk Matrix
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
## Recommendation
Evidence-based recommendation with caveats.
## Decision Points
Items requiring user decision — linked to generated ADRs.ADR Requirements
This assessment must produce at least one ADR:
Required: "Rewrite vs Modernize"
- Context: Summary of assessment findings
- Options: Full rewrite, partial rewrite (strangler fig), incremental modernization
- Decision criteria: Effort, risk, timeline, team capability, business constraints
- Recommendation: Based on evidence, not preference
- Consequences: What each option means for the next 6–18 months
Optional ADRs (trigger when relevant):
- Strangler fig approach: When partial rewrite is recommended, detail the decomposition strategy
- Target stack selection: When multiple target stacks are viable, compare them
- Data migration strategy: When data model changes significantly between stacks
Important Notes
- A rewrite is rarely the right answer for the reasons people think. Present evidence, not opinions.
- The "second system effect" is real — acknowledge it in the risk analysis.
- Partial rewrites (strangler fig pattern) are often the pragmatic middle ground. Always evaluate this option.
- If the user hasn't specified a target stack, ask before proceeding. Assessment without a target is meaningless.
- Effort estimates should include ramp-up time, testing, migration, and parallel-run periods — not just coding.
- Do not minimize the cost of knowledge embedded in existing code. Implicit behavior is expensive to rediscover.
Mandatory Completion Checklist
The orchestrator MUST verify ALL of the following before marking rewrite-assessment as complete:
-
specs/assessment/rewrite.mdexists with: feasibility rating, effort comparison (rewrite vs modernize), risk analysis, and target stack evaluation - A rewrite-vs-modernize recommendation is stated with supporting evidence
- Strangler fig (partial rewrite) option is explicitly evaluated
- Data migration complexity is assessed
- At least one ADR exists in
specs/adrs/documenting the rewrite/modernize decision - State JSON and audit log are updated
BLOCKING: If any item is unchecked, the skill has NOT completed successfully. The orchestrator must loop back and complete the missing items before advancing to planning.
© EmeaAppGbb, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .github/skills/rewrite-assessment of EmeaAppGbb/spec2cloud.
Open the folder on GitHubat commit 8e76618
Compare with similar skills
Rewrite Assessment next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Rewrite Assessment this skillEmeaAppGbb/spec2cloud | 100 | — | ~2k | Automated safety check: Pass | MIT | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Cto AdvisorIbrahim-3d/orchestrator-supaconductor | 381 | 4 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Architecture DecisionDonchitos/Claude-Code-Game-Studios | 26k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Improve Codebase Architectureywwynm/EverythingDone | 144 | 15 repos | ~1.3k | Automated safety check: Pass | GPL-3.0 | |
| Domain Modelingbrim-borium/spotify_sdk | 166 | 5 repos | ~806 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Cto Advisor
Ibrahim-3d/orchestrator-supaconductor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.
Architecture Decision
Donchitos/Claude-Code-Game-Studios
Create an ADR documenting a technical decision: context, alternatives considered, consequences.
Improve Codebase Architecture
ywwynm/EverythingDone
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/.
Domain Modeling
brim-borium/spotify_sdk
Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.
Design Doc Mermaid
SpillwaveSolutions/design-doc-mermaid
Create Mermaid diagrams (flowchart, sequence, class, ER, state, C4, architecture) from text or source code.
More from EmeaAppGbb/spec2cloud
All 38 skills in this repoAzure Deployment
EmeaAppGbb/spec2cloud
Provision Azure infrastructure, deploy to Azure Container Apps, and verify via smoke tests.
Contract Generation
EmeaAppGbb/spec2cloud
Generate API contracts, shared TypeScript types, and infrastructure resource definitions from Gherkin scenarios and test files.
Ddd Modeling
EmeaAppGbb/spec2cloud
Create Domain-Driven Design proposals from product specs or brownfield extraction outputs.
Implementation
EmeaAppGbb/spec2cloud
Write application code to make failing tests pass using contract-driven, slice-based architecture.
Spec Refinement
EmeaAppGbb/spec2cloud
Review PRDs and FRDs through product and technical lenses. An agent skill from EmeaAppGbb/spec2cloud.
State Management
EmeaAppGbb/spec2cloud
Read, write, and maintain .spec2cloud/state.json across phases and increments.
Related
Categories
Questions about Rewrite Assessment
What does Rewrite Assessment do?
Assess feasibility and effort of rewriting the application in a different language, framework, or architecture. Rewrite Assessment is an agent skill from EmeaAppGbb/spec2cloud. Assess feasibility and effort of rewriting the application in a different language, framework, or architecture.
When should I use Rewrite Assessment?
Rewrite Assessment fits situations like: tasks that involve Architecture decision records.
How do I install Rewrite Assessment in Claude Code?
Run `npx skills add EmeaAppGbb/spec2cloud --skill rewrite-assessment -a claude-code`. Or copy the skill folder (.github/skills/rewrite-assessment in EmeaAppGbb/spec2cloud) into .claude/skills/rewrite-assessment in your project. Claude Code loads it when a task matches its description.
How do I install Rewrite Assessment in Codex?
Run `npx skills add EmeaAppGbb/spec2cloud --skill rewrite-assessment -a codex`. Or copy the skill folder (.github/skills/rewrite-assessment in EmeaAppGbb/spec2cloud) into .agents/skills/rewrite-assessment in your project. Codex loads it when a task matches its description.
Can I use Rewrite Assessment in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add EmeaAppGbb/spec2cloud --skill rewrite-assessment -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rewrite-assessment, .gemini/skills/rewrite-assessment, .github/skills/rewrite-assessment and .opencode/skills/rewrite-assessment in your project.
What does Rewrite Assessment need to run?
SKILL.md names no scripts, command-line tools or credentials: Rewrite Assessment is instructions for the agent only.
Does Rewrite Assessment access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Rewrite Assessment safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Rewrite Assessment use?
Rewrite Assessment is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Rewrite Assessment use?
About 2k tokens (SKILL.md is roughly 8.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Rewrite Assessment?
Skills that share tags, products or a category with Rewrite Assessment: PR Design Doc (OpenHands/OpenHands, 90k stars), Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 381 stars), Architecture Decision (Donchitos/Claude-Code-Game-Studios, 26k stars) and Improve Codebase Architecture (ywwynm/EverythingDone, 144 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Rewrite Assessment?
EmeaAppGbb (a GitHub organization) maintains it in EmeaAppGbb/spec2cloud, which has 100 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on April 16, 2026.
Source: EmeaAppGbb/spec2cloud on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.