Hi! First off — great toolkit. The pipeline design and skill quality are really impressive.
I'm setting this up in an existing repo that doesn't have the docs/ structure the skills expect, and I ran into a bit of a cold-start problem. Several skills reference convention/template files in their <repo_conventions> sections:
• docs/DOCS.md
• docs/projects/DOCS.md
• docs/_templates/milestone.md
• docs/_templates/issue.md
• docs/_templates/project.md
• docs/process/LINEAR.md
• docs/process/GRAPHITE.md
These are referenced across spec-to-milestone, harden-milestone, milestone-to-issues, prework-sweep, and linear-method, but there aren't any example versions included in the repo or docs. The getting-started.md guide mentions creating the project folder structure but doesn't cover these files.
Would it be possible to include minimal starter versions of these files — either as examples in docs/ or as a scaffolding script? Even bare-bones templates with just the expected section headings would save a lot of guesswork for people adopting the toolkit in existing projects.
Thanks for sharing this!
Hi! First off — great toolkit. The pipeline design and skill quality are really impressive.
I'm setting this up in an existing repo that doesn't have the docs/ structure the skills expect, and I ran into a bit of a cold-start problem. Several skills reference convention/template files in their <repo_conventions> sections:
• docs/DOCS.md
• docs/projects/DOCS.md
• docs/_templates/milestone.md
• docs/_templates/issue.md
• docs/_templates/project.md
• docs/process/LINEAR.md
• docs/process/GRAPHITE.md
These are referenced across spec-to-milestone, harden-milestone, milestone-to-issues, prework-sweep, and linear-method, but there aren't any example versions included in the repo or docs. The getting-started.md guide mentions creating the project folder structure but doesn't cover these files.
Would it be possible to include minimal starter versions of these files — either as examples in docs/ or as a scaffolding script? Even bare-bones templates with just the expected section headings would save a lot of guesswork for people adopting the toolkit in existing projects.
Thanks for sharing this!