Write modular feature specifications with six sections and Mermaid diagrams.
npx skills add https://github.com/YuluoY/nimis --skill spec-writing-yuluoy
Please help me install this Agent Skill. Skill: spec-writing Source: https://github.com/YuluoY/nimis/tree/main/skills-en/spec-writing Command: npx skills add https://github.com/YuluoY/nimis --skill spec-writing-yuluoy
Transform vague or incomplete feature requests into modular, reviewable, and acceptance-ready requirement documents so teams can implement and test with confidence. It prevents omissions, reduces back-and-forth clarification, and produces versionable artifacts suitable for PR review and TDD.
Write a six-section feature spec for "guest checkout" including Mermaid flowchart for the user journey, an ER diagram for any new entities, and an explicit test combination matrix, then save it to specs/checkout/guest-checkout.md.
High-intent search queries and answers about installing and using this skill.
To write structured PRDs from vague ideas, transform incomplete feature requests into modular six-section feature specifications. This standardizes user stories, requirement descriptions, and acceptance criteria into reviewable documents for confident team implementation.
The best way to include visual flowcharts and ER models in feature specs is using Mermaid-first diagrams. It requires plain-text Mermaid diagrams for logic, module, sequence, architecture, and ER visuals, alongside plain-text directory trees for file structures.
Yes, you can generate requirement documents for monorepos and multi-module systems. It applies monorepo defaults with apps/ and packages/ directories, splitting multi-module requirements into separate per-feature Markdown files under the specs/ directory.
To create a cross-combination test matrix for TDD, generate explicit test matrices within the Test Criteria section. It automatically assigns P0–P3 priorities to guide QA and test-driven development, ensuring versionable artifacts suitable for PR review.
The required sections for a standardized feature specification are Feature Overview, User Stories, Requirement Description, Technical Requirements, Constraints, and Test Criteria. This six-section enforcement prevents omissions and reduces back-and-forth clarification.
Yes, spec-writing works for incremental feature slices and requirement reviews. It transforms incomplete requests into acceptance-ready documents, making them suitable for incremental feature slicing and modular requirement reviews within versionable artifacts.
sibukixxxTransform vague business ideas into structured technical requirements and user stories.
GDSDNGenerate test design documents with levels and priorities from story requirements.
Hyeonjun0527Enforce monorepo boundaries between apps/* and packages/* directories.
matteocervelliConvert feature descriptions into INVEST-compliant user stories with YAML and Markdown exports.
