track-new

Standardize creation and lifecycle management of tracked work items.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/owebboy/maestro --skill track-new
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: track-new
Source: https://github.com/owebboy/maestro/tree/main/skills/track-new
Command: npx skills add https://github.com/owebboy/maestro --skill track-new

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of inconsistent project tracking and poorly defined work items by enforcing a structured lifecycle for features, bugs, chores, and refactors.

Core Features & Use Cases

  • Structured Work Items: Automatically generates standardized specifications and tracks them via a pluggable work-item store.
  • Lifecycle Management: Guides the user through a rigorous process from classification and specification gathering to planning and artifact linking.
  • Use Case: When starting a new feature, use this skill to ensure the requirements, acceptance criteria, and technical notes are documented and linked to a formal implementation plan before writing any code.

Quick Start

Use the track-new skill to initialize a new feature work item for the user authentication module.

Frequently Asked Questions about track-new

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

FAQPage Schema
How do I standardize feature and bug tracking for a new development project?

Standardize feature and bug tracking by enforcing a structured lifecycle that guides classification, specification gathering, and technical planning before implementation begins. This ensures requirements and acceptance criteria are documented consistently.

What is the best way to document technical specifications before writing code?

Documenting technical specifications involves gathering requirements, defining acceptance criteria, and linking artifacts within a project-scoped directory structure. This process ensures all technical notes are formally tracked before development starts.

How does lifecycle management work for tracked work items like chores and refactors?

Lifecycle management for tracked work items works by guiding users through a rigorous process from initial classification to specification gathering, technical planning, and artifact linking. This enforces consistent development progress across features, bugs, and refactors.

Can I integrate external work-item stores with my project tracking workflow?

Yes, you can integrate external work-item stores with your project tracking workflow. The system standardizes creation and lifecycle management while connecting to external stores and agentic workflows to maintain consistent development progress.

Do I need a project-scoped directory structure to manage development specifications?

Yes, a project-scoped directory structure is needed to manage development specifications effectively. It facilitates artifact linking and ensures that tracked work items, technical plans, and specifications remain organized within the project environment.