plan

To generate structured markdown plans for a GitHub repository, use the plan skill to draft plan bodies from a standard template and save them under the plan/ directory with timestamped filenames. It enforces frontmatter fields and consistent naming for project alignment.

Linking a markdown project plan to a CSV issue tracker is done by generating a matching issues CSV file that references the drafted plan. The workflow automatically creates these CSV issue references to track tasks directly alongside your plan documents.

Yes, you can use a standard template to draft repo plans while enforcing required frontmatter fields. The skill applies template-based plan bodies and performs basic validation through provided scripts to ensure consistent document structure.

The plan skill requires no external dependencies to save files under the plan/ directory and generate issue contracts. It operates independently using provided scripts and assets to draft and validate your project plans.

Using repo-local plans instead of manually tracking issues reduces ambiguity and aligns team expectations by drafting structured plan documents and associated issue contracts. This approach enforces consistent naming and frontmatter validation for reliable tracking.