Skip to content

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

fskill-creator

Verified

Create, maintain, or migrate functional skills; supports creating from a requirement brief and migrating an existing legacy skill directory into a functional skill structure.

functions/resolve_task_mode.md

View on GitHub
# resolve_task_mode

## Purpose

Determine whether this `fskill-creator` invocation should go through the create, migrate, enhance, or validate lane based on user input.

## Input

| Field | Required | Description |
|---|---:|---|
| `task_mode` | no | User-explicit `create`, `migrate`, `enhance`, or `validate`. |
| `skill_request` | no | User's natural language request for the target skill. |
| `legacy_skill_dir` | no | Path to a legacy skill directory. |
| `legacy_skill_path` | no | Deprecated alias for `legacy_skill_dir`; may also be a direct path to `SKILL.md`. |
| `legacy_skill_content` | no | Legacy skill markdown content. |
| `existing_skill_files` | no | Existing functional skill files. |

## Output

| Field | Description |
|---|---|
| `task_context.mode` | Normalized `create`, `migrate`, `enhance`, or `validate`. |
| `task_context.reason` | Rationale for the decision. |
| `task_context.required_lane_outputs` | Lane outputs that must be provided subsequently, e.g. `create_context` or `migration_context`. |
| `task_context.open_questions` | Questions needing user clarification when safe judgment is not possible. |

## Logic

1. If the user explicitly passed a valid `task_mode`, use it.
2. If `legacy_skill_dir`, `legacy_skill_path`, or `legacy_skill_content` is present, choose `migrate`.
3. If `existing_skill_files` is present and the request involves completion, enhancement, adding functions, or adding report/tests, choose `enhance`.
4. If the request only asks to check or validate an existing skill, choose `validate`.
5. Otherwise, choose `create`.
6. If `migrate` lacks a legacy source, or `create` lacks an understandable skill request, return an open question.

## Errors

| Code | When |
|---|---|
| `[UNKNOWN_TASK_MODE]` | `task_mode` is not a supported enum value. |
| `[INSUFFICIENT_TASK_INPUT]` | Cannot determine task type from the input. |

## Observability

Record resolved mode, reason, open question count, and required lane outputs.
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: 469kUpdated Claude CodeCodexVerifiedInstall
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