What problem does it solve? It prevents knowledge loss by capturing both finished knowledge articles and in-the-moment development questions as GitHub Issues in the dio0550/dev-knowledge repository, each tagged with a label indicating how the knowledge should later be merged into the repository. ## Core Features & Use Cases - Article Registration: Register a knowledge article (created with knowledge-article) as an issue, using the article's frontmatter title and body. - Question Ticketing: File lightweight issues for design doubts, open questions, or things to investigate later, using a structured body template. - Mandatory Workflow Labels: Every issue gets exactly one of two labels: knowledge:pr (investigate on a branch, create the knowledge md via PR) or knowledge:direct (work on main and push the md directly). - Use Case: While coding, you hit a design question you can't resolve now. Run the skill to file an issue titled with the question, labeled knowledge:pr, so it becomes a tracked TODO for later article writing. ## Quick Start Create a GitHub issue in the dev-knowledge repository for this design question with the knowledge:pr label.
