niwashi-06-harvest

To extract reusable patterns from narrative documentation, you provide completed build artifacts like the narrative-spec, sections-checklist.json, and Git logs to distill concrete design decisions into a structured pattern document.

Generating a pattern document requires a narrative that has passed REVIEW, along with its build history, narrative-spec, sections-checklist.json, and Git logs to derive actionable design decisions for future RESEARCH phases.

Pattern extraction from Git logs and build history works by analyzing commit records and specifications to surface concrete design decisions, which are then structured into narrative arc, interaction, visual, and revision sections.

You can merge newly extracted narrative patterns with existing pattern files to build a consolidated knowledge base, ensuring successive RESEARCH phases can reference a unified set of reusable design decisions.

The best way to document design decisions is to harvest them into niwashi_docs/patterns/<concept-type>.md files, organizing details into explicit narrative arc, interaction, visual, revision, and reuse sections.

You should not use automated pattern extraction if your narrative has not yet passed REVIEW, or if you lack the required build history, narrative-spec, sections-checklist.json, and Git logs needed to derive accurate patterns.