tlc-plan

Turns a request, ticket, PRD, design or thread into one plan a human approves and a builder can act on without the conversation: asks every gray area until no product decision is left to the builder, then writes the problem, EARS criteria with concrete values, the path and the data it touches (drawn in mermaid), the interface, and only the decisions that are hard to reverse. Captures that come with the request bind. Use when the user says "plan this", "plan feature", "specify feature", "write th

Install

KitScout test notes

Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.

Similar tools

• karpathy-guidelines 232,709 ★
  Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code t
• discernment-nudge 193,970 ★
  After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted art
• timeline-report 116,728 ★
  Generate a "Journey Into [Project]" narrative report analyzing a project's entire development history from cla
• weekly-digests 116,728 ★
  Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline i
• what-the 116,728 ★
  What the? Use when the user wants a plain-English breakdown of something technical — the who, what, where, why