Convert discussion summaries into structured Markdown Design Notes with decisions, assumptions, and acceptance criteria.
npx skills add https://github.com/AntonBespalov/WC_IST --skill dn-writer
Please help me install this Agent Skill. Skill: dn-writer Source: https://github.com/AntonBespalov/WC_IST/tree/main/.codex/skills/dn-writer Command: npx skills add https://github.com/AntonBespalov/WC_IST --skill dn-writer
This Skill converts collaborative discussions and decisions into formal, publishable Design Notes (DNs) that capture what was decided, why, and what evidence or rollback is required. It anchors requirements, interfaces, timing, risks, and verification in canonical documentation.
Convert the latest discussion summary into a complete Markdown Design Note using the standard template.
High-intent search queries and answers about installing and using this skill.
To convert architecture discussions into formal design notes, summarize the meeting outcomes into a structured Markdown document. This anchors decisions, requirements, and verification plans in canonical documentation for review and rollback.
Documenting requirements decisions and rollback planning is best achieved by generating a formal Design Note. It captures what was decided, the evidence required, and assumptions into a structured Markdown template for traceable verification.
Yes, design note generation works for both software and hardware projects. It produces canonical documentation that captures interfaces, timing, risks, and requirements, ensuring decisions are traceable across diverse engineering disciplines.
To structure a decision record using a design note template, populate a Markdown document conforming to the standard DN structure. Include frontmatter, assumptions, dependencies, acceptance criteria, and verification links for review.
Yes, you can link design notes directly to existing project context and safety plans. The generated document references canonical files like docs/PROJECT_CONTEXT.md and related verification plans to ensure complete traceability.
A design note for software architecture verification should include decisions, assumptions, dependencies, acceptance criteria, and rollback planning. It conforms to a standard Markdown template to anchor requirements in canonical documentation.
zm2231Generate structured markdown summaries of work sessions with outcomes, decisions, action items, and learnings.
brainbrewlabsFormat Markdown, reStructuredText, and AsciiDoc documentation files for publication.
clovernguyen1010-ship-itGuide technical design decisions for scalable backend and API architectures.
xenitV1Systematize requirements analysis and ADR documentation for architecture decisions.
