feature-document

Gap analysis maps undocumented design decisions and missing requirements to ensure complete feature specs. It highlights gaps between the initial feature idea and the explicit, testable requirements needed before implementation begins.

Gap analysis in feature documentation maps undocumented design decisions and missing requirements to ensure complete specs. It highlights gaps between the initial feature idea and the explicit, testable requirements needed before implementation begins.

You link feature requirements to epics and wiki content by sourcing context from related second-brain pages during the documentation stage. This ensures all generated specs maintain traceability with existing project artifacts.

Yes, you can decompose epics into testable specs by processing tasks entering the document stage. The Skill generates explicit requirements and maps design decisions, ensuring the decomposed specs are sourced from related wiki pages.

Existing wiki pages are not strictly required to generate a feature artifact, but they are highly beneficial. The Skill sources related second-brain pages to ensure requirements are explicit, testable, and linked for full traceability.