lane-todo-hygiene

Enforce lane-scoped TODO creation with proposed status and review metadata.

1|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/pweiskircher/pi-lanes --skill lane-todo-hygiene
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lane-todo-hygiene
Source: https://github.com/pweiskircher/pi-lanes/tree/main/skills/lane-todo-hygiene
Command: npx skills add https://github.com/pweiskircher/pi-lanes --skill lane-todo-hygiene

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents accidental or unmanaged creation of TODOs in pi lanes by enforcing lane-scoped TODO discipline and ensuring LLM suggestions do not become active work without review.

Core Features & Use Cases

  • Enforces that LLM-created TODOs are recorded as proposed items and not auto-started.
  • Specifies required metadata for proposed TODOs, including createdBy, needsReview, and a short proposal reason.
  • Provides reviewer guidance to decide whether to approve, edit, or reject proposed TODOs during lane workflows in the CLI or dashboard.
  • Use case: when an assistant suggests follow-up work during onboarding or a lane session, capture it as a proposed TODO for human review rather than starting work automatically.

Quick Start

Ask the assistant to propose a lane TODO for follow-up work and ensure it is created as proposed and marked for review.

Frequently Asked Questions about lane-todo-hygiene

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent LLM-created TODOs from auto-starting in lane workflows?

To prevent LLM-created TODOs from auto-starting in lane workflows, this Skill enforces that all LLM suggestions are recorded as proposed items with needsReview set to true, requiring explicit human CLI or dashboard approval before any state changes occur.

What metadata is required when proposing a lane TODO from an assistant?

When proposing a lane TODO from an assistant, the required metadata includes createdBy set to llm, needsReview set to true, and a short proposalReason explaining the suggestion, ensuring every item is traceable and marked for human review.

How do I manage lane-scoped TODOs in the CLI and dashboard without accidental auto-starts?

You can manage lane-scoped TODOs safely by applying this Skill to the pi lanes workflow, CLI, and dashboard, which ensures only lane_propose_todo or explicit human actions change TODO state, preventing unmanaged creation.

Why do my chat-only TODOs disappear instead of being tracked in pi lanes?

Chat-only TODOs disappear because they lack proper lane context and metadata. This Skill enforces lane-scoped TODO discipline by capturing LLM suggestions as proposed items with createdBy and proposalReason fields, ensuring they are recorded for review rather than lost.

Can I approve or edit proposed TODOs directly from the pi lanes dashboard?

Yes, you can approve, edit, or reject proposed TODOs directly from the pi lanes dashboard or CLI. This Skill provides reviewer guidance to help decide whether to accept LLM-proposed items before they become active work.