spec-driven-translation

Translate and modernize codebases through PRD, specification, and implementation plans.

Updated Oct 28, 2025

Search Tags:#documentation #spec-driven #validation #translation #PRD #project-management #code-migration

Ready to run

npx skills add https://github.com/JonahSussman/project-eris --skill spec-driven-translation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-translation
Source: https://github.com/JonahSussman/project-eris/tree/main/.claude/skills/spec-driven-translation
Command: npx skills add https://github.com/JonahSussman/project-eris --skill spec-driven-translation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill implements a documentation-first, validation-driven workflow to translate or modernize a codebase. It guides work by producing a Product Requirement Document (PRD), a Project Specification, an Implementation Plan, and a Task Execution Checklist, then iterates with remediation until success.

Core Features & Use Cases

PRD-driven planning: Capture purpose, constraints, and acceptance criteria upfront.
Structured design docs: Generate Project Specification and Implementation Plan to align teams.
Iterative validation loop: Choose, implement, validate, and remediate with a bounded retry budget until requirements are satisfied.

Quick Start

Provide your repository and target technology, then ask the Skill to generate PRD, Project Specification, and Implementation Plan, followed by an iterative task cycle.

Frequently Asked Questions about spec-driven-translation

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

FAQPage Schema

How do I plan a codebase migration across frameworks or languages?▼

Spec-driven translation creates a structured migration plan by generating a Product Requirement Document, Project Specification, and Implementation Plan upfront. This documentation captures scope, constraints, acceptance criteria, and validation milestones before implementation begins, reducing rework and alignment gaps.

What's the best way to validate a code migration is complete and correct?▼

A validation-driven workflow iterates through choose-implement-validate cycles with externally-verifiable milestones and evidence-rich commits. Each cycle tests against predefined acceptance criteria, then remediates failures within a bounded retry budget until all requirements pass.

How do I extract and preserve business logic during a code translation?▼

Spec-driven translation ingests your source tree to extract intents, constraints, SLAs, and integrations. This analysis feeds the PRD and Project Specification, ensuring business rules and dependencies are captured and carried forward into the modernized codebase.

Can I use a documentation-first approach for SDK upgrades or framework rewrites?▼

Yes. Spec-driven translation applies to migrations or translations across frameworks, SDKs, or languages. It covers migration scope, validation criteria, testing, and iterative remediation with a task execution checklist tailored to your upgrade path.

What happens if validation fails during migration?▼

The workflow enters remediation with a bounded retry budget. Failed validation triggers evidence-rich commits documenting the failure, then implements fixes and re-validates. This cycle repeats until acceptance criteria are satisfied or the retry budget is exhausted.

Do I need project management tools to use spec-driven translation?▼

No external tools are required. Spec-driven translation produces a Project Specification, Implementation Plan, and Task Execution Checklist as deliverables. These can integrate with your existing project management workflow or stand alone as migration guidance.