Writes Japanese software design documents with structured sections and decision criteria.
npx skills add https://github.com/pokutuna/dotfiles --skill design-doc-pokutuna
Please help me install this Agent Skill. Skill: design-doc Source: https://github.com/pokutuna/dotfiles/tree/main/claude/skills/design-doc Command: npx skills add https://github.com/pokutuna/dotfiles --skill design-doc-pokutuna
High-intent search queries and answers about installing and using this skill.
Invoke the skill with /design-doc and describe the feature or system you are designing. It produces a Japanese document with sections like Objective, Background, Goals, Scenarios, and Open Issues, following your project template if one exists.
Core sections are Title, Objective, Background, Goals, and Non-Goals. Additional sections such as Scenarios, Interfaces, Security, SLOs, Monitoring, and Open Issues are selected based on the design target and the cost of being wrong; irrelevant sections are omitted rather than left blank.
Detail is proportional to the cost of being wrong. Decisions that are expensive to reverse, like programming language or storage choices, get constraints, options, and trade-offs; easily changed decisions get a reasonable choice without lengthy discussion.
Yes. When asked to check for gaps, it uses its section catalog as a checklist to identify missing considerations and high-stakes undecided issues. For review-only requests it returns findings without rewriting the whole document.
Yes. If the project has a template or notation rules, it follows that structure and section naming, applying only the guidance for each section's content. Without a template it uses its standard section set with English headings and Japanese body text.
hfadhlullahGenerate Product Requirements Documents through an interview process.
blundergoatBreak down software implementation tasks into risk-weighted milestones with verification gates.
vorynkavitaliyIdentify STRIDE threats with category mappings and mitigation guidance.
patricio0312revGenerate RFC-style technical proposals with problem statements, solutions, alternatives, risks, and rollout plans.
