一键在 Manus 中运行任何 Skill

migrate-subfeatures

星标3

分支1

更新时间2026年7月12日 03:40

Migrates legacy feature-local change packets into durable subfeatures for repositories that still use the old changes/ layout.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

sirius-cc-wu

sirius-cc-wu/sirius-skills

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Migrate Subfeatures

Use this skill when a repository still contains legacy planning artifacts from the old change-based workflow and those artifacts need to be converted into the current durable subfeatures/ model.

Responsibilities

Resolve one feature or the full planning tree.
Detect legacy changes/<change-id>/ packets.
Convert legacy .feature-change-meta.json into .subfeature-meta.json.
Create migrated subfeature folders whose lifecycle is stored in .subfeature-meta.json.
Rebuild feature-local subfeature registries and resync the planning registry.

Preferred Input

a feature slug, folder name, or path when migrating one feature
or --all for a repo-wide migration
optional --dry-run before modifying planning files

Required Output

migrated subfeatures under docs/features/<feature>/subfeatures/<subfeature-id>/
rebuilt subfeatures/README.md and subfeatures/registry.json
refreshed top-level planning registry via guide-planning
a JSON migration report listing candidates, migrations, and blockers

Workflow

Run scan to inspect legacy changes/ packets and detect blockers.
Run migrate --dry-run to preview target paths and metadata mapping.
Run migrate for one feature or --all for the whole planning tree.
Review the JSON report for migrated items and any conflicts left behind.

Tooling

# Scan one feature for legacy change packets
sirius migrate-subfeatures scan "checkout"

# Scan the whole planning tree
sirius migrate-subfeatures scan --all

# Preview migration without writing changes
sirius migrate-subfeatures migrate \
  "checkout" \
  --dry-run

# Migrate every legacy feature in the planning tree
sirius migrate-subfeatures migrate --all

Guardrails

Do not overwrite an existing target subfeature folder.
Do not rewrite discovery, design, or breakdown contents beyond structural migration needs.
Do not use this skill for net-new feature planning; use guide-planning and add-subfeature for those.
Prefer --dry-run before repo-wide migration.

同仓库更多 Skills

同仓库

bootstrap

sirius-cc-wu/sirius-skills

Bootstraps `.skills/planning.json`, `.skills/execution.json`, and `.skills/conventions.json` for a repository, and can also scaffold a wiki knowledge layer next to the planning feature directory. Use when a user asks to configure a project, initialize `sirius-skills` settings, apply generic defaults, add Jira-oriented conventions, or bootstrap the repo's wiki skeleton.

2026-07-163

add-subfeature

sirius-cc-wu/sirius-skills

Canonical workflow for creating and managing durable subfeatures under an existing feature. Use this whenever the user asks to add, create, start, open, or bootstrap a subfeature so downstream planning skills keep the expected metadata and discovery-draft lifecycle.

2026-07-123

autoplan

sirius-cc-wu/sirius-skills

Reconcile one planning target, optionally execute planning owners in sequence, and persist checkpointed resume context through approval, optional auto-commit handoff, and planning-commit handoff.

2026-07-123

breakdown

sirius-cc-wu/sirius-skills

Converts repo stories and planning docs into directly executable, dependency-aware work items with traceability and execution handoff.

2026-07-123

close-slice

sirius-cc-wu/sirius-skills

Closes the active execution slice with validation and records durable closure metadata while invoking shared owner-completion reconciliation.

2026-07-123

design

sirius-cc-wu/sirius-skills

Produces feature-level system-design.md artifacts before breakdown when a feature needs architecture, interface, constraint, failure-handling, or validation decisions captured durably.

2026-07-123

name	migrate-subfeatures
description	Migrates legacy feature-local change packets into durable subfeatures for repositories that still use the old changes/ layout.

Migrate Subfeatures

Use this skill when a repository still contains legacy planning artifacts from the old change-based workflow and those artifacts need to be converted into the current durable subfeatures/ model.

Responsibilities

Resolve one feature or the full planning tree.
Detect legacy changes/<change-id>/ packets.
Convert legacy .feature-change-meta.json into .subfeature-meta.json.
Create migrated subfeature folders whose lifecycle is stored in .subfeature-meta.json.
Rebuild feature-local subfeature registries and resync the planning registry.

Preferred Input

a feature slug, folder name, or path when migrating one feature
or --all for a repo-wide migration
optional --dry-run before modifying planning files

Required Output

migrated subfeatures under docs/features/<feature>/subfeatures/<subfeature-id>/
rebuilt subfeatures/README.md and subfeatures/registry.json
refreshed top-level planning registry via guide-planning
a JSON migration report listing candidates, migrations, and blockers

Workflow

Run scan to inspect legacy changes/ packets and detect blockers.
Run migrate --dry-run to preview target paths and metadata mapping.
Run migrate for one feature or --all for the whole planning tree.
Review the JSON report for migrated items and any conflicts left behind.

Tooling

# Scan one feature for legacy change packets
sirius migrate-subfeatures scan "checkout"

# Scan the whole planning tree
sirius migrate-subfeatures scan --all

# Preview migration without writing changes
sirius migrate-subfeatures migrate \
  "checkout" \
  --dry-run

# Migrate every legacy feature in the planning tree
sirius migrate-subfeatures migrate --all

Guardrails

Do not overwrite an existing target subfeature folder.
Do not rewrite discovery, design, or breakdown contents beyond structural migration needs.
Do not use this skill for net-new feature planning; use guide-planning and add-subfeature for those.
Prefer --dry-run before repo-wide migration.