requirements-doc-creator

To create a requirements document from a Lean Canvas, this Skill extracts known information and interactively asks one question at a time to fill gaps, outputting a structured Stage 1 system requirements definition for your startup.

The best way to handle missing information during product planning is to mark unknowns with (要確認) and assumptions with (仮定), allowing you to proceed without stalling while making uncertainties visible for later review.

The two-phase requirements creation process works by first generating a Stage 1 system requirements document, then pausing for an explicit user review gate before proceeding to create the Stage 2 detailed requirements specification.

Yes, you can track design decisions and risks while defining system requirements, as the Skill outputs template-based structured documents that explicitly include design decision logs and risk/assumptions sections.

No, you do not need complete product planning materials to start defining requirements; the Skill uses dialogue-driven gap completion to interactively collect any missing required information from you one question at a time.