ogt-docs-create-task_skill

This skill helps you create and manage task documents in the docs/todo workflow, enabling full lifecycle control from pending to done with verification.
  • Python

2.6k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill ogt-docs-create-task

  • _meta.json296 B
  • SKILL.md20.9 KB

Overview

This skill creates and manages task documents inside the docs/todo/ workflow. It automates creation of task folders and files, moves tasks between lifecycle stages, and enforces required signals for verification. Use it to maintain consistent task metadata, progress logs, and lifecycle transitions.

How this skill works

The skill inspects the docs/todo/ directory structure, creates or updates task folders (pending, in_progress, review, blocked, done, rejected, implemented) and required files such as task.md, progress.md, implementation.md, verification.md, and signal files (e.g., .ready_for_review, .verified). It validates presence and content of control files (.version, .priority, timestamps, assignment markers) and performs atomic moves between stage folders, ensuring verification signals are present before marking done or implemented.

When to use it

  • Create a new work item in docs/todo/pending
  • Start work and move a task to in_progress with assignment and timestamp
  • Mark a task ready for review and attach .pr_link and .ready_for_review
  • Block a task with .blocked_reason and .depends_on entries
  • Verify completion and move to done with .verified and .completed_at
  • Mark verified work as implemented and record .implemented_at and .release_version

Best practices

  • Always include a clear task.md with Summary, Objectives, and Acceptance Criteria
  • Keep a .version file in JSON to track schema and creation time
  • Set .priority (critical|high|medium|low) at creation
  • Use progress.md to capture incremental updates and timestamps
  • Use empty signal files (presence-only) for stage transitions and require accompanying metadata (e.g., .blocked_reason, .pr_link)
  • Perform moves atomically and verify required signal files before changing final states

Example use cases

  • Create docs/todo/pending/fuzzy_search/ with task.md, context.md, .version, .priority
  • Start work: add .assigned_to_{agent} and .started_at in in_progress/card_variants/ and update progress.md
  • Request review: add implementation.md, .ready_for_review, .pr_link, and .review_requested_at in review/spell_routes/
  • Block a task: add .blocked, .blocked_reason, .blocked_at and .depends_on in blocked/auth_refactor/
  • Complete and verify: add verification.md, .verified, .completed_at and .verified_by_{agent} in done/ogt_cli_commands/
  • Release implemented work: add .implemented_at and .release_version in implemented/creatures_index/

FAQ

Add verification.md describing tests performed, create an empty .verified file, set .completed_at timestamp, and optionally add .verified_by_{agent}; then move the folder into done/.

How should assignment be recorded?

Create an empty .assigned_to_{agent} file inside the task folder and set .started_at when work begins; update progress.md with work logs.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
ogt-docs-create-task skill by openclaw/skills | VeilStrat