Skip to content

AGI-comming/functional-skill-creator / skills/fskill-creator/sub-skills/migrate

fskill-creator-migrate

Verified

Migrate lane for fskill-creator; analyzes a legacy skill directory into behavior map, function split proposal, and source evidence.

functions/map_existing_behavior.md

View on GitHub
# map_existing_behavior

## Purpose

Identify legacy behaviors that must be preserved during migration.

## Input

| Field | Required | Description |
|---|---:|---|
| `legacy_skill` | yes | Loaded source skill package data. |
| `migration_constraints` | no | User-provided behavior preservation or refactoring constraints. |

## Output

| Field | Description |
|---|---|
| `behavior_map.goals` | Existing skill goals and non-goals. |
| `behavior_map.external_inputs` | Expected inputs of the legacy skill. |
| `behavior_map.outputs` | Outputs, file writes, or side effects. |
| `behavior_map.rules` | Rules that must be preserved. |
| `behavior_map.platform_assumptions` | Runtime, tool, or environment assumptions. |
| `behavior_map.companion_assets` | Existing references, scripts, tools, and testcases that must be preserved or explicitly replaced. |
| `behavior_map.risks` | Behavior preservation risks and ambiguous areas. |

## Logic

1. Extract goals, commands, decision rules, file scopes, tool assumptions, and output requirements from `SKILL.md`.
2. Scan `references/`, `scripts/`, and other companion files for additional rules, schemas, and deterministic behavior.
3. Preserve explicit ordering constraints from the legacy skill.
4. Distinguish behavior from wording/style.
5. Put unclear or conflicting rules into `risks`; do not silently resolve.

## Errors

| Code | When |
|---|---|
| `[MISSING_LEGACY_SKILL]` | Missing `legacy_skill.markdown`. |
| `[NO_BEHAVIOR_FOUND]` | Not enough behavior in source to migrate. |

## Observability

Record counts of goals, inputs, outputs, rules, assumptions, companion assets, and risks.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 468kUpdated Claude CodeCodexUnverifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 321kUpdated Claude CodeCodexVerifiedInstall