Conversation
The aidd-pm templates already declare `type` (task, story, epic, spike, defect); the aidd-dev ones did not, so every plan and phase lands on the kanban board as `type: unknown` - 49 of 49 parents on this repository's own board - and the board's --type filter has nothing to match. The plan templates now stamp `type: plan`, the phase template `type: phase`, and the for-sure init-tracking action names the field it must fill. A ratchet test keeps the next status-bearing template from shipping untyped: every plugin template under assets/ that stamps `status:` must name its `type:` in the same frontmatter.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The aidd-pm templates already declare
type(task, story, epic, spike, defect); the aidd-dev ones did not, so every plan and phase lands on the kanban board astype: unknown- 49 of 49 parents on this repository's own board - and the board's --type filter has nothing to match. The plan templates now stamptype: plan, the phase templatetype: phase, and the for-sure init-tracking action names the field it must fill.A ratchet test keeps the next status-bearing template from shipping untyped: every plugin template under assets/ that stamps
status:must name itstype:in the same frontmatter.🎯 What & why
🛠️ How it works
🧪 How to verify
🔗 Linked issue
Closes #
✅ I certify