Document design decisions, deviations, tradeoffs, and open questions for a completed issue as HTML.
npx skills add https://github.com/smallnest/goal-workflow --skill note-it
Please help me install this Agent Skill. Skill: note-it Source: https://github.com/smallnest/goal-workflow/tree/main/skills/note-it Command: npx skills add https://github.com/smallnest/goal-workflow --skill note-it
This Skill helps teams preserve the reasoning behind implemented code so important context is not lost after an issue is built and reviewed. It turns ad hoc notes into a consistent HTML record that explains what changed, why it changed, and what still needs follow-up.
Ask the skill to create implementation notes for the current issue and save them as an HTML file in docs with the required issue number.
High-intent search queries and answers about installing and using this skill.
To document implementation rationale before shipping, you capture design decisions, deviations, tradeoffs, and open questions for a completed issue. This creates a structured HTML record explaining what changed and why it changed for reviewers.
Recording design decisions and tradeoffs for issue tracking involves documenting the implementation approach and highlighting spec gaps or future questions. This preserves the reasoning behind implemented code so important context is not lost after review.
To generate HTML implementation notes, you resolve the issue number and use a fixed four-section template. The skill outputs the final rationale record as an HTML file located at docs/issue#XXXX.html.
Yes, you can create pre-ship documentation for issue-driven development workflows. It generates a structured checkpoint after implementation and review fixes, allowing reviewers to quickly understand non-obvious choices before the code ships.
Yes, generating implementation notes requires the issue implementation to be already reviewed. It applies to workflows where review fixes are finished and a final rationale record is needed to document deviations and open questions before shipping.
Implementation notes fail to capture design decisions when they lack a structured template. Using a fixed four-section format ensures you consistently record deviations, tradeoffs, and open questions tied to the specific issue number.
dEitY719Fetch a GitHub issue by number and print a structured verbatim summary.
kuro0107Generate delivery inventory and _meta.md distribution metadata for a PUBLISH_V version.
marchattonAnalyze pull request review comments, implement code changes, and report resolutions.
hulusi-tuncDocument feature accessibility decisions, tradeoffs, and WCAG compliance mappings.
