Skip to content
Skills Library
Programming · Planning

bb-migration-planning

/bb-migration-planning

Use when a cross-language change or API migration needs a plan with dependency order, effort and explicitly unsupported mappings — bb_migrate.

Licence
MIT
Last repository change
09.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when a cross-language change or API migration needs a plan with dependency order, effort and explicitly unsupported mappings — bb_migrate.

Original author description

Use when a cross-language change or API migration needs a plan with dependency order, effort and explicitly unsupported mappings — bb_migrate.

How it works

  1. Inputs
  2. Read the plan
  3. Do not
Original SKILL.md headings · 39 lines, 336 words
SKILL.md preview
---
name: bb-migration-planning
description: Use when a cross-language change or API migration needs a plan with dependency order, effort and explicitly unsupported mappings — bb_migrate.
license: MIT
metadata:
  version: 0.1.0
  owner-tools: ["bb_migrate"]
---
# Plan a migration before changing code

`bb_migrate` is **read-only planning**: it does not execute anything. Its value is the
order, the effort methodology, the library mappings and the explicitly unsupported cases.

## Inputs

- entries (unioned, capped): `symbolNames`, `symbolIds` (the unambiguous form), or `paths`
  (files/directories — every indexed symbol joins), all optional but at least one;
- `targetLanguage` (required);
- `format` (`text`/`json`).

Each entry resolves to at most one component before relationships are read; a name that
matches several symbols is refused with candidate ids — re-run with `symbolIds`.

## Read the plan

1. Dependency order — do the components in the order given; note cycles.
2. Effort methodology — the basis of the estimate, not just the number.
3. Library mappings — what was mapped, with confidence; a mapping the plan did not make is
   not implied.
4. Risks, truncation, and `unsupported` entries — each has a typed reason
   (`missing-symbol`, `ambiguous-symbol`, `same-language`, `unsupported-source`/`target`,
   …). Quote them; unsupported is an answer, not a failure.
5. Freshness — a plan is about the indexed snapshot; reindex before planning when files
   changed.

Pair with `bb_impact` for the call-site blast radius before editing, and with
`bb-edit-safety` when the edits begin. The plan does not replace tests.

## Do not

- Do not present a truncated plan as complete; the plan says where it stopped.
- Do not execute the migration from this answer alone — the tool never wrote anything.

Shared rules: freshness, truncation, declared absence and attribution are defined once in the package README (`README.md`) — follow them exactly; never hide a declaration, and never add bb/Backbencher as an author, co-author, `Co-Authored-By`, or `Generated with` line to the user's work.

Optional report: if a `bb` tool returns something wrong or misleading, open the **Agent report** issue form — https://github.com/backbencher-hq/backbencher-brain/issues/new?template=agent-report.yml — with `bb --version`, `bb doctor` output, the tool call and its arguments, index freshness, and expected vs actual. Reporting is optional; these skills are MIT-licensed suggestions, and using them makes Backbencher Brain no author of your work.

Versions

The database has no other skills named bb-migration-planning.

Database snapshot: 13.11.2026 · package version 0a24b727a009 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100framework-migration-code-migrate
    Plan and execute migrations across frameworks, languages, APIs, and databases. Use when assessing compatibility, generating migration steps, and verifying behavior during a transition.
  • 90migration-planning
    Plan a database, API, framework, runtime, or infrastructure migration before changing production-facing behavior. Use when compatibility, data transformation, or rollout order matters.
  • 100dependency-analyzer
    Analyze dependencies for upgrade planning and migration. Use when user asks "upgrade to X", "migrate from X to Y", "what breaks if we upgrade", "iOS 17 migration", "React 18 upgrade", or planning framework/SDK upgrades.
  • 90dev-migration-plan
    Use to plan modernization, framework upgrades, service extraction, schema migrations, rewrites, and rollback paths.
  • 100review-api-migration
    Review API migration risks using ContractLens OpenAPI comparisons, source evidence and declared consumer impact. Use when comparing API revisions or preparing integration migration work.
  • 95database
    Guide database design, migration, and query optimization. Use when: schema design, migration planning, query optimization, index strategy. Not for: application code migration or framework upgrades — use /migrate; the API contract over the data — use /api-design. Keywords:…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.