Loading...
Loading...
Found 11 Skills
Use when an outcome is stated, inferred, or hidden.
Plan and ship a game under a jam deadline: lock scope to the clock, schedule the hours, cut features, and submit on time. Use for a game jam (Ludum Dare, GMTK Jam, Global Game Jam), a 48-hour or weekend build, or scoping and submitting a jam entry.
You are **SeniorProjectManager**, a senior PM specialist who converts site specifications into actionable development tasks. You have persistent memory and learn from each project.
Diagnose requirements problems and guide discovery of real needs and constraints
Rapid implementation for small, low-risk, well-defined changes. Use when the task is narrow in scope, has clear acceptance criteria, and can be completed safely without a formal multi-phase plan.
Feature specification and planning guidelines for software engineers. This skill should be used when writing PRDs, defining requirements, managing scope, prioritizing features, or handling change requests. Triggers on tasks involving feature planning, specification writing, stakeholder alignment, or scope management.
Zero-ceremony inline execution for tasks completable in 3 or fewer file edits. No plan, no subagent, no research — just understand, do, commit, log. Use for "quick fix", "typo fix", "one-line change", "trivial fix", "rename this variable", "update this value", "fix this import". Do NOT use for tasks requiring research, planning, new dependencies, or more than 3 file edits — redirect to /quick instead.
【Retired on 2026-07-27, do not trigger this skill】All capabilities have been merged into issue-pool — see issue-pool/references/plan-writing.md for the 7-step framework planning process. For any requests related to "writing plan reports / framework plans / project plans / v1.0 plans / version roadmaps / phase solutions", please use issue-pool instead. This directory is only retained as historical archive and will no longer be pushed to any targets.
Implement an already-decided bounded scope from a Plan, handoff, review findings, direct brief, docs task, fix, or refactor. Use for implementation or continuation work; use diagnose-issue first when the cause is unknown.
Use this when you are about to start Discover for an existing project, but you don't know "which portals can be used as evidence (run/test/ci/contract/ops)" and "which modules should be prioritized (P0/P1/P2)", and you are worried that out-of-control scope will lead to unmaintainable results.
Implement one accepted, bounded work card with immediate local verification, invariant preservation, and zero scope drift. Use when executing a planned work card, applying a well-defined code change, implementing an isolated function, or performing targeted single-scope edits — even if the user does not explicitly say "fable-execute" (e.g. "implement this card", "write the code for this step", "apply the agreed changes", "build this component"). Do NOT use when new architectural decisions are required (use fable-plan) or when tests are repeatedly failing (use fable-recover).