w-02-light-task-workflow

Plan and manage single-page tasks with approval gates and live checklists.

27|4|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/Foxfire1st/agents-remember --skill w-02-light-task-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: w-02-light-task-workflow
Source: https://github.com/Foxfire1st/agents-remember/tree/main/.cursor/skills/w-02-light-task-workflow
Command: npx skills add https://github.com/Foxfire1st/agents-remember --skill w-02-light-task-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In-between task workflow for projects that require a durable task file, clear approval gates, and a focused single-page plan, ensuring work is properly scoped and auditable.

Core Features & Use Cases

  • Light-task-workflow orchestrates planning, approval, and live checklists for scoped tasks.
  • It supports escalation to a master + sub-task series when plans outgrow a single page, within a shared worktree.
  • It emphasizes drift checks, onboarding propagation, and governance checks via the coordination framework.

Quick Start

Create a task wrapper under your task-root, generate task.md from template.md, and begin planning with an explicit approval gate.

Frequently Asked Questions about w-02-light-task-workflow

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

FAQPage Schema
How do I manage lightweight planning tasks with formal approval gates?

Lightweight planning tasks are managed using a single-page task file that enforces a formal approval gate before execution. This workflow ensures scoped work is properly audited and checked for drift before implementation begins.

What is the best way to track in-between project tasks in a shared worktree?

In-between tasks in a shared worktree are tracked using a durable task wrapper and a live execution checklist. This approach maintains lifecycle governance and applies drift checks to keep work properly scoped.

How do I escalate task plans when they outgrow a single page?

When task plans outgrow a single page, you escalate them to a master and sub-task series within the shared worktree. This escalation preserves the durable task file lifecycle while expanding scope.

Do I need a coordination framework to enforce governance checks on task checklists?

A coordination framework is required to enforce governance checks, onboarding propagation, and memory-quality controls. It validates the live execution checklist and ensures ongoing task alignment across the worktree.

When should I use a single-page task plan instead of a master and sub-task series?

A single-page task plan is used for scoped, lightweight tasks requiring quick approval gates and direct execution. If plans outgrow this page, escalate to a master and sub-task series to maintain auditability.

Why does my task workflow require drift checks and onboarding updates?

Drift checks and onboarding updates are required to maintain memory-quality controls and governance across the shared worktree lifecycle. They ensure the live execution checklist remains aligned with the formal approval gate.