agents-remember: Skill for Claude Code

w-02-light-task-workflow Light Task Workflow

This skill is the thin orchestration contract for the in-between case: work that needs a durable task file, an explicit approval gate, distinct implementation examples, and decision tracking, but still fits a single-page implementation plan as a rule of thumb.

Companion Files

1. workflow.md
2. template.md
3. master-template.md

When To Use

Use this workflow when:

1. the work needs a durable task file, an approval gate, and decision tracking
2. the implementation plan can still fit on a single page as a rule of thumb
3. the target may be non-code or a small isolated code change, provided the lighter single-page plan remains a good fit

Treat the single-page-plan test as guidance rather than a hard routing rule. When the work outgrows a single page — richer artifacts, broader coordination, or a sprawling plan — escalate to a master + light sub-task series (master-template.md) rather than forcing it into one light task.

Task Artifact

Light-task-workflow maintains one task wrapper folder under <task-root>/, where <task-root> is returned by c-08-ar-coordination-context-resolver for the target repository. The task document is always named task.md inside that wrapper folder.

Naming convention:

1. ticket-linked: YYMMDD_#<number>_<short-slug>/task.md
2. organic: YYMMDD_<descriptive-slug>/task.md

Create the wrapper folder at the same time the durable task artifact is created, before any c-09-git-worktree-manager worktree exists. Use template.md as the canonical scaffold. Implementation steps and substeps are tracked with checkboxes, and that checklist is the live execution state during implementation. When code changes are in scope, the task file also carries proposed code examples for each distinct change type so the developer can review the intended implementation shape before approval.

Light-task artifacts use minute-precision timestamps in YYYY-MM-DDTHH:MM format wherever they record task-local dates or times.