Generate and maintain markdown screen specs from source code and git diffs.
npx skills add https://github.com/seiei-sogen/tumigi --skill dev-screen-spec
Please help me install this Agent Skill. Skill: dev-screen-spec Source: https://github.com/seiei-sogen/tumigi/tree/main/skills/dev-screen-spec Command: npx skills add https://github.com/seiei-sogen/tumigi --skill dev-screen-spec
Manually creating and maintaining screen specification documents is time-consuming and prone to drift as source code changes or acceptance criteria evolve. This skill automates the full lifecycle of screen spec management to ensure documentation stays accurate and aligned with your project's current state.
Ask the AI to generate a screen specification document for your new checkout page from the existing source code, or update all changed screen specs after you commit modifications to the payment flow.
High-intent search queries and answers about installing and using this skill.
You can generate screen specification documents from source code by parsing routing definitions, page components, form elements, validation rules, and interaction logic to produce structured markdown with source file traceability.
To keep screen spec docs in sync with web application changes, the skill detects source code modifications via git diff and incrementally updates only the affected sections of existing markdown documents to eliminate manual maintenance.
Yes, you can create screen specs from acceptance criteria and plan documents before implementation, allowing you to establish design alignment and structured documentation prior to writing any source code.
Yes, this screen spec generator supports grouped screen management for large web projects, organizing generated markdown specifications and maintaining traceability across complex application structures.
Screen specification documents integrate with downstream web test planning workflows by providing structured markdown outputs that detail routing, page components, and interaction logic needed for test generation.
matthewdeavesGenerate markdown hardware test plans from phase-based plan documents.
stravinestGenerate exhaustive test scenarios and QA reports from a codebase.
ajsai47Update project markdown documentation by cross-referencing git diffs after code commits.
guidodinelloList commits authored by the current git user that touch a specified path.
