gpsaggese/helpers / .claude/skills/auto_task.create_specs_from_todos
auto_task.create_specs_from_todos
VerifiedCreate a plan for fixing a list of TODOs
Goal
- Given a list of TODOs in a file from the user, create a plan to fix them
Workflow
Understand Each TODO
- Each TODO is in the form
<FILE>:<LINE_NUM>:<TODO description>- E.g.,
./helpers/hmarkdown_coloring.py:235:def colorize_bullet_points_in_slide(...
- E.g.,
- Read each TODO and understand the problem
- If it's a bug:
- Find the root cause
- Run experiments to verify the issue and its root cause
- Devise a plan to fix the problem and a plan to verify the fix
Write the Fix Plan
- Create a plan
tasks.mdusing the template.claude/templates/auto_task.template.md - Fill in the template's
* Repo:checklist per.claude/skills/auto_task.rules.mdsection "Multi-Repo Issues, Branches, and PRs" (how to tell which repo a<FILE>belongs to, and how to handle TODOs spanning more than one repo) - Say in the plan file how it was generated, with this comment at the top:
<!-- Generated by `.claude/skills/auto_task.create_specs_from_todos/SKILL.md` --> - Write the comments as bullet points per
.claude/skills/markdown.rules.mdand.claude/skills/text.rules.md, with minimal text - Do not change the code, only propose the fixes
Follow the Conventions
- Follow
.claude/skills/auto_task.rules.mdsection "Follow the Coding and Testing Rules"- Refer to
.claude/skills/coding.*/SKILL.mdand.claude/skills/testing.*/SKILL.mdfor the repo's best practices
- Refer to
- For bugs, add unit tests that fail before the fix and pass after it (red/green approach)
- For renaming, check the entire code base so everything is updated
- Follow
.claude/skills/coding.rename/SKILL.md
- Follow
- For a change of function signature, update all the calling instances
Rank the Issues
- Order the issues by increasing complexity, starting with the fixes of high confidence
Verification
-
tasks.mdcontains one issue block per input TODO - Every issue block has type, reason, proposed fix, confidence, complexity, and verification plan filled in
- Issues are ordered by increasing complexity, starting from the highest confidence fixes
- No code was changed, only the plan file was written
- The plan file says that it was generated by
.claude/skills/auto_task.create_specs_from_todos/SKILL.md
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |