Plan todo research
Skill Abbiirr/plan-todo-workflow/plugins/plan-todo-workflow/skills/plan-todo-research
Run deep research for a PLAN/TODO/TESTING workflow, create or update all workflow docs, and persist research context under temp-research/. Use when the user invokes research mode.From its SKILL.md
npx -y skills add Abbiirr/plan-todo-workflow --skill plan-todo-researchAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.6 KB, as published. Nobody here has run it
Plan Todo Workflow: Research
Preferred slash command in Claude/Puku: /plan-todo-research.
You are in research mode for the Plan Todo Workflow plugin.
Start by running:
./bin/planflow research
./bin/planflow prompt research
Then create or update PLAN.md, TODO.md, and TESTING.md from the research. Identify the next open checklist item unless the user names a specific task.
Research mode must produce durable research context in temp-research/:
research-log.md: findings, evidence, commands run, source links, and decisions.assumptions.md: assumptions, risks, unknowns, and open questions.web-searches.md: search queries, source URLs, dates, and relevance notes.context-summary.md: compact summary for later agent turns so raw notes do not need to be reread.
Research mode must also produce implementation-ready workflow docs:
PLAN.md: goal, scope, approach, references, assumptions, risks, and decisions.TODO.md: granular checklist items withPLAN.mdreferences andTESTING.mdgates, ordered so an agent can complete them unattended in the sequential loop.TESTING.md: verification criteria, commands, manual checks, and closing gates that are executable by the agent whenever possible.
Rules:
- Never produce git-write workflow content unless the user explicitly asks for git work.
PLAN.md,TODO.md,TESTING.md, andtemp-research/notes must not instruct, script, or gate on mutating git commands such asgit add,git commit,git push,git stash,git reset,git rebase, branch creation, checkout, or merge. Verification gates must depend on code, tests, imports, runtime checks, and read-only inspection, not staging or commit state. - Design the workflow for unattended completion by the sequential loop. Avoid gates that require the user unless external credentials, production access, or an unavoidable manual approval is truly required; record those as explicit blockers.
- Do not edit implementation code in research mode unless the user explicitly asks.
- Use web search when current external facts, APIs, docs, changelogs, package behavior, or examples matter.
- Keep private chain-of-thought out of files. Save concise rationale, evidence, assumptions, and decisions instead.
- Keep
temp-research/useful but compact; summarize aggressively incontext-summary.md. - End by stating whether the item is ready for
implement.