Review inputs
- repoPath (string, required): pulled from od project import.
- targetStack (form): collected by rewrite-plan.
- testCommand / buildCommand (string, optional): overrides
nexu-io/open-design
od-code-migration
Default reference pipeline for the code-migration taskKind — code-import → design-extract → token-map → rewrite-plan → patch-edit ↔ build-test devloop → diff-review → handoff.
59Collecting
See source evidenceView GitHub source
npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/scenarios/od-code-migration"Source profileReview and auditCatalog only
Source checked Jul 28, 2026·Refresh due Oct 26, 2026
Limited to facts supported by the pinned source
What the pinned source establishes about od-code-migration
Spec §1 / §10.1 / §20.3 / §21.3.2 / §23.3.3: the canonical code-migration flow. The pipeline cannot ship an accept decision without a passing build — the patch-edit ↔ build-test devloop is the convergence engine.
npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/scenarios/od-code-migration"The pinned source contains about 138 English words and 2 usable sections. That evidence supports a source profile, not a complete guide.
138 source words · 2 usable sections
What the source actually contains
2 verifiable source sections for od-code-migration
Sections are extracted automatically from the pinned SKILL.md and link back to the source.
Default pipeline
The scenario uses build.passing && tests.passing as the convergence signal — promoted into the spec §22.4 vocabulary by the build-test atom.
The scenario uses build.passing && tests.passing as the convergence signal — promoted into the spec §22.4 vocabulary by the build-test atom.
Required user inputs
A plugin built on this scenario typically declares od.inputs:
repoPath (string, required): pulled from od project import.targetStack (form): collected by rewrite-plan.testCommand / buildCommand (string, optional): overrides
Choose a different workflow
When another Skill is the better fit
ab-testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.
Open source detaildesign-review
Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.
A separate implementation from event4u-app/agent-config; compare its source, maintenance signals, and permission requirements.
Open source detailhexagonal-architecture
Design, implement, and refactor Ports & Adapters systems with clear domain boundaries, dependency inversion, and testable use-case orchestration across TypeScript, Java, Kotlin, and Go services.
A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.
Open source detailFAQ
How do I install od-code-migration?
The source record exposes this install command: npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/scenarios/od-code-migration". Inspect the command and pinned source before running it.
Repository stars
82,073
Repository forks
9,485
Quality
59/100
Source repository last pushed
Quality breakdown
Based on traceable docs and repository signals; stars are not treated as quality.
Documentation15/30
Specificity12/25
Maintenance20/20
Trust signals12/25
Compare before choosing
Related Agent Skills and source variants
These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.
ab-testing by coreyhaines31
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
design-review by event4u-app
Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.
hexagonal-architecture by affaan-m
Design, implement, and refactor Ports & Adapters systems with clear domain boundaries, dependency inversion, and testable use-case orchestration across TypeScript, Java, Kotlin, and Go services.
playwright-architect by event4u-app
Use when shaping a Playwright suite — locator strategy, Page Object boundaries, fixture composition, flake-prevention architecture, CI-vs-local split — even on 'design our E2E tests'.
playwright-testing by event4u-app
Use when writing Playwright E2E tests — browser automation, visual regression testing, Page Objects, fixtures, and reliable test patterns.
View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 1 min
od-code-migration (scenario)
Spec §1 / §10.1 / §20.3 / §21.3.2 / §23.3.3: the canonical
code-migration flow. The pipeline cannot ship an accept decision
without a passing build — the patch-edit ↔ build-test devloop is
the convergence engine.
Default pipeline
{
"stages": [
{ "id": "import", "atoms": ["code-import"] },
{ "id": "tokens", "atoms": ["design-extract", "token-map"] },
{ "id": "plan", "atoms": ["rewrite-plan"] },
{
"id": "verify",
"atoms": ["patch-edit", "build-test"],
"repeat": true,
"until": "(build.passing && tests.passing) || iterations>=8"
},
{ "id": "review", "atoms": ["diff-review"] },
{ "id": "handoff", "atoms": ["handoff"] }
]
}
The scenario uses build.passing && tests.passing as the
convergence signal — promoted into the spec §22.4 vocabulary by
the build-test atom.
Required user inputs
A plugin built on this scenario typically declares od.inputs:
repoPath(string, required): pulled fromod project import.targetStack(form): collected byrewrite-plan.testCommand/buildCommand(string, optional): overrides the inferred package.json scripts in thebuild-testatom.
- Source repo
- nexu-io/open-design
- Skill path
- plugins/_official/scenarios/od-code-migration/SKILL.md
- Commit SHA
- 89d6d4ef21ba
- Repository license
- Apache-2.0
- Data collected