From tac
Generates detailed chore plans in specs/*.md from a one-line description for maintenance, cleanup, refactoring, and dependency updates. Use /chore or auto-activation.
npx claudepluginhub melodic-software/claude-code-plugins --plugin tacThis skill is limited to using the following tools:
Create a new plan in `specs/*.md` to resolve the Chore using the exact specified markdown Plan Format. Follow the Instructions to create the plan, use the Relevant Files to focus on the right files.
Breaks down multi-step work into small 2-5 minute tasks with verification criteria, dependencies, and logical ordering. Saves dynamic plans as {task-slug}.md in project root. For features, refactoring.
Creates specs and phased file-level implementation plans for features, bugs, refactors by researching codebase with search, graph queries, and context files.
Generates concrete execution plans from vague objectives using Implementation Intentions framework. Specifies actions, targets, tools, and conditions for complex tasks or multi-step operations.
Share bugs, ideas, or general feedback.
Create a new plan in specs/*.md to resolve the Chore using the exact specified markdown Plan Format. Follow the Instructions to create the plan, use the Relevant Files to focus on the right files.
Focus on the following files to understand the codebase:
Write the plan to specs/chore-<descriptive-name>.md using this exact format:
# Chore: <descriptive-name>
## Chore Description
<Clear explanation of what needs to be done and why this is valuable>
## Relevant Files
<List all files that will be created, modified, or deleted>
## Step by Step Tasks
1. <First specific, actionable task>
2. <Second specific task with file references>
3. <Continue with numbered tasks>
## Validation Commands
<Commands that prove the work is complete>
- Run `<command>` to verify <what>
- Run `<command>` to verify <what>
## Notes
<Edge cases, dependencies, gotchas, or related work to consider>
$ARGUMENTS