Quest Chain Decomposer

Break a fuzzy, high-friction goal into a sequenced quest chain with prerequisite nodes, parallel branches, waiting points, Definition of Done, and the first...

Security Scan

The skill's code, instructions, and requirements are consistent with a local planning/authoring helper and do not request unrelated credentials, installs, or network access.

Purpose & Capability

The name/description (decompose goals into quest chains) match the code and SKILL.md: handler.py contains templates, category rules, blueprints, and starter actions for organizing goals. There are no unrelated required binaries, env vars, or config paths.

Instruction Scope

SKILL.md instructs the agent to produce a markdown plan and the handler implements text parsing and templating. The code reads the local SKILL.md for metadata but does not reference system paths, credentials, or external endpoints. Instructions do not request broad system data or exfiltration.

Install Mechanism

No install spec is provided (instruction-only style), and included code is a local Python handler and tests. There are no downloads, package installs, or archive extracts declared that would write arbitrary code to disk at install time.

Credentials

The skill declares no required environment variables or credentials. The handler uses standard libraries (os, json, re) and only reads its own SKILL.md file; there are no requests for unrelated secrets or config paths.

Persistence & Privilege

always is false and the skill does not appear to modify other skills or system-wide settings. It does not request persistent privileges or autonomous overrides beyond normal agent invocation.

Assessment

This skill appears internally consistent and local: it templates and formats plans from user input. If you want extra assurance, inspect the full handler.py (it reads SKILL.md and runs purely local logic), run the included tests in a sandboxed Python environment, and ensure you only provide the goal text (no secrets).

Chinese name: 任务链分解器.

Overview

Use this skill to turn a large or messy objective into a practical quest chain. It keeps the first step small, shows dependencies, and avoids fake progress such as endless research without a deliverable.

When to use

Use this skill when the user wants to:

• break a goal into a realistic sequence
• identify prerequisite, parallel, and waiting nodes
• define what “done” means for each step
• start today instead of circling the task
• re-route after blockers appear

Example prompts

• "Break this project into a quest chain"
• "I know what I want, but I cannot find the first step"
• "Map the dependencies for this admin task"

Inputs

Useful inputs include:

• goal or deliverable
• deadline or time window
• success definition
• resources and constraints
• blockers, approvals, or handoffs

Workflow

1. Clarify the finish line.
2. Sort work into main quest, prerequisite nodes, parallel branches, and waiting points.
3. Give each step a clear Definition of Done.
4. Make the first move small enough to start immediately.
5. Add reroute rules for common stalls.

Output

Return markdown with:

• main quest objective
• quest chain map
• Definition of Done by step
• starter trio
• reroute rules

Limits

• This skill does not replace full project management software.
• For large cross-team schedules, it should stay at the planning level.
• If the goal itself is unclear, define the mission first before decomposing it.

Acceptance Criteria

• The first quest is small enough to start now.
• Dependencies are visible.
• Each step has an explicit done line.
• The plan points toward a real deliverable, not just thinking about the work.