Menu
SkillsMP has collected 10 skills from eiei114/pi-takt-marionette. Open a skill to review its source and details.
Showing 10 of 10 collected skills.
Resolve the exact TAKT target, intent, and execution constraints before any setup, planning, queueing, or run. Internal preflight phase; use through takt-pi-next-step or takt-pi-orchestrator, not as a generic TAKT front door.
Choose the next concrete action in a TAKT project and route into the correct built-in workflow. Use when the user asks what to do next, where the TAKT task stands, how to continue, what remains, or wants an ask-matt-style flow guide after setup, planning,…
Act as the front door for TAKT in Pi: resolve the exact target, automatically bootstrap missing project-local TAKT state and profiles, decide whether the request needs task planning, execution, recovery, or next-step navigation, then route to the specialized…
Finish TAKT preflight by showing the final task body, obtaining enqueue confirmation, and verifying the directly persisted TAKT workflow before execution. Internal preflight phase; use through takt-pi-next-step or takt-pi-task-planner.
Turn a vague request into one concrete TAKT pending task through a Pi-side planning conversation, then persist it directly without starting execution. Use after takt-pi-orchestrator routes a queue request or when the user explicitly invokes…
Turn one explicit PRD into child tickets and queue them as one ordered aggregate TAKT task on one spec branch. Use when a user wants the grill → spec → TAKT queue flow, asks to stack implementation work in TAKT, or wants a PRD converted into a bridge-owned…
Prepare an exact TAKT project before workflow selection or task planning: create local .takt scaffolding, copy one safe preset, and register the named profile. Internal preflight phase; use through takt-pi-next-step or takt-pi-orchestrator.
Hold the final explicit execution gate after TAKT preflight: verify pending work and ask whether to run all queued tasks. Internal preflight phase; use through takt-pi-next-step or takt-pi-task-planner.
Select and lock the exact standalone TAKT workflow during preflight using the effective project > user-global > builtin catalog. Internal preflight phase; use through takt-pi-next-step or takt-pi-orchestrator.
Execute finalized issue and development tasks through TAKT using Pi-only agents, a named project profile, and the Pi stacked raw-output widget. Use after takt-pi-orchestrator routes an execution or recovery request, or when the user explicitly invokes…