القائمة
Migrates legacy feature-local change packets into durable subfeatures for repositories that still use the old changes/ layout.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
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.
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.
Converts repo stories and planning docs into directly executable, dependency-aware work items with traceability and execution handoff.
Closes the active execution slice with validation and records durable closure metadata while invoking shared owner-completion reconciliation.
Produces feature-level system-design.md artifacts before breakdown when a feature needs architecture, interface, constraint, failure-handling, or validation decisions captured durably.
| name | migrate-subfeatures |
| description | Migrates legacy feature-local change packets into durable subfeatures for repositories that still use the old changes/ layout. |
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.
changes/<change-id>/ packets..feature-change-meta.json into .subfeature-meta.json..subfeature-meta.json.--all for a repo-wide migration--dry-run before modifying planning filesdocs/features/<feature>/subfeatures/<subfeature-id>/subfeatures/README.md and subfeatures/registry.jsonguide-planningscan to inspect legacy changes/ packets and detect blockers.migrate --dry-run to preview target paths and metadata mapping.migrate for one feature or --all for the whole planning tree.# 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
guide-planning and
add-subfeature for those.--dry-run before repo-wide migration.