new-track

Convert a brief feature or bug description into spec.md and plan.md files with a unique Track ID.

39|6|Updated Jan 21, 2026

Search Tags:#workflow #spec #plan #feature #product-management #context-driven #track

Ready to run

npx skills add https://github.com/mayurpise/draft --skill new-track

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: new-track
Source: https://github.com/mayurpise/draft/tree/main/skills/new-track
Command: npx skills add https://github.com/mayurpise/draft --skill new-track

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly spawn a new development track by translating a brief description into a formal spec and a phased plan, grounded in the Context-Driven Development workflow.

Core Features & Use Cases

Generate a standardized spec.md and plan.md for a new track from a concise description.
Create a unique Track ID in kebab-case and avoid overlaps with existing tracks.
Pre-checks load project context (product.md, tech-stack.md, architecture.md) to ensure alignment with a real context.

Quick Start

Use the new-track skill to create a track with the description "Add user authentication" which will generate spec.md and plan.md grounded in the project context.

Frequently Asked Questions about new-track

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

FAQPage Schema

How do I generate a development spec and plan from a short feature description?▼

To generate a development spec and plan, provide a brief feature or bug description to create a fully structured track. It outputs deterministic spec.md and plan.md artifacts with a unique Track ID for Context-Driven Development workflows.

What is a context-driven development track and when do I need one?▼

A context-driven development track is a structured workflow artifact for features, fixes, or refactors. You need one to translate a brief description into a formal spec and phased plan grounded in your project's product, tech stack, and architecture documents.

Does creating a new track require existing project architecture documents?▼

Yes, creating a new track requires existing project architecture documents. Pre-checks load product.md, tech-stack.md, and architecture.md to ensure the generated spec.md and plan.md align with your actual project context.

How do I ensure my generated Track ID does not overlap with existing tracks?▼

To ensure your generated Track ID does not overlap, the track creation process automatically generates a unique Track ID in kebab-case. It checks against existing tracks to prevent naming collisions.

Can I use this workflow for bug fixes and refactoring or only new features?▼

You can use this workflow for bug fixes and refactoring, not only new features. It applies to feature work, fixes, and refactors within a project context to produce structured spec and plan artifacts.