planning

Create and maintain TODO.adoc, ROADMAP.adoc, and BACKLOG.adoc with task traceability.

4|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/cuioss/plan-marshall --skill planning-cuioss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/cuioss/plan-marshall/tree/main/marketplace/bundles/pm-requirements/skills/planning
Command: npx skills add https://github.com/cuioss/plan-marshall --skill planning-cuioss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plans and organizes project work by providing standards for creating and maintaining planning documents that ensure task tracking, status indicators, and traceability to requirements.

Core Features & Use Cases

  • Establishes a consistent document structure (TODO.adoc, ROADMAP.adoc, BACKLOG.adoc) and header format.
  • Enables hierarchical task organization, status tracking, and traceability from tasks to requirements and specifications.
  • Supports living documentation with guidance on maintenance and ongoing updates across project cycles.

Quick Start

Follow the Planning Document Standards to create and maintain a TODO.adoc that links tasks to requirements and specifications.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I create planning documents with traceability from tasks to requirements?

To create planning documents with traceability, you structure TODO.adoc, ROADMAP.adoc, and BACKLOG.adoc files to hierarchically organize tasks and link them directly to requirements and specifications. This establishes consistent status tracking across project cycles.

What is the best way to maintain living documentation across project cycles?

Maintaining living documentation involves applying standardized structures and ongoing updates to your planning files. This approach keeps TODO.adoc, ROADMAP.adoc, and BACKLOG.adoc current, ensuring task tracking and traceability remain accurate throughout project cycles.

How do I organize a project backlog and roadmap using AsciiDoc?

You organize a project backlog and roadmap using AsciiDoc by applying standardized header formats to BACKLOG.adoc and ROADMAP.adoc files. This enables hierarchical task organization, status tracking, and traceability to project specifications.

Does standardized planning documentation support hierarchical task organization?

Yes, standardized planning documentation supports hierarchical task organization. By structuring planning files like TODO.adoc, it enables clear status tracking and maintains traceability from tasks to requirements and specifications.

When do I need to use standardized planning documents for project management?

You need standardized planning documents when organizing project work and ensuring task tracking. They provide consistent structures for TODO.adoc, ROADMAP.adoc, and BACKLOG.adoc, establishing status indicators and traceability to requirements across project cycles.