From yukti
Produce a phased implementation plan for a task. Reads files, identifies risks, breaks work into small verifiable phases. Runs on Opus. Does NOT write code — produces a plan for review before implementation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/yukti:planplannerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Produce a phased plan for this task:
Produce a phased plan for this task:
$ARGUMENTS
If the user has provided a file list (from a prior /yukti:explore call or pasted from the explorer), use it. If not, read the task carefully and identify the files yourself with Grep/Glob before planning.
Follow your system prompt rules. Output the structured plan only — no code, no preamble. Stop after the plan; do not implement.
npx claudepluginhub akii09/yukti --plugin yuktiGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Provides Slack GIF creation utilities with dimension/FPS/color constraints and Python PIL-based frame generation. Use for animated Slack emoji or message GIFs.