07-tasks

Standardize repository task creation, documentation, and lifecycle progression in tasks/ directories.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Pandaala/Edgion --skill 07-tasks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 07-tasks
Source: https://github.com/Pandaala/Edgion/tree/main/skills/07-tasks
Command: npx skills add https://github.com/Pandaala/Edgion --skill 07-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents task chaos by standardizing how work is created, documented, reviewed, and archived inside the repository’s tasks/ structure.

Core Features & Use Cases

  • Task directory conventions: Organizes work across lifecycle axes (todo/pending) and review-batch axes (review-*).
  • Profiles with required artifacts: Guides creation of feature, investigation, review-batch, and docs/single-file tasks with the right document set.
  • Phase-driven workflow: Defines what to do per lifecycle phase and which skills/documents to load, ensuring outputs are produced at every step.
  • Status tracking and checklists: Standardizes status values, completion rules, and implementation checkpoints to reduce missed steps.
  • Templates for consistent documentation: Provides a main task template and workflow/format companion guidance for multi-step feature work.

Quick Start

Create a new task under tasks/pending/ with a kebab-case name and start by writing the required <task-name>.md main file plus a 00-context.md skills list.

Frequently Asked Questions about 07-tasks

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

FAQPage Schema
How do I standardize repository task management and lifecycle phases for feature work?

Standardize repository task management by creating tasks in a tasks/ directory using profile-specific artifact sets and phase-driven workflows. This enforces consistent task structure, tracks status values across lifecycle phases like pending and todo, and coordinates required files for feature development.

What is the best way to track code review batches and investigations in a repository?

Track code review batches and investigations by organizing work across review-batch axes like review-* and applying profile-specific artifact sets. This generates required documents and standardizes status tracking to reduce missed steps during the review output and investigation lifecycle.

How do I create a new task and start writing required documentation?

Create a new task under tasks/pending/ using a kebab-case name, then write the required main task-name.md file along with a 00-context.md skills list. This initial document set drives the phase-driven workflow and determines which skills to load for subsequent phases.

Does this task management approach work for small docs updates and hotfix tracking?

Yes, this task management approach works for small docs updates and hotfix tracking by using specific task profiles. It guides the creation of docs or single-file tasks with the right document set while applying phase pruning rules and on-demand document generation.

When should I apply phase pruning rules during the task lifecycle?

Apply phase pruning rules during the task lifecycle when progressing between phases to ensure outputs are produced at every step. Pruning removes obsolete context and coordinates required files, ensuring only relevant implementation checkpoints and status tracking documents remain active.