maestro-knowhow

To capture reusable decisions and tips, you provide a natural-language intent and the system infers the entry type, writing structured knowhow directly into `.workflow/knowhow/`. This eliminates the need to manually decide the format up front.

Saving an architecture decision record is best handled by inferring the entry type from your request and storing it as a structured knowledge entry in `.workflow/knowhow/`. This ensures the decision is persisted for later reuse across sessions.

Yes, you can store debugging recipes and templates without defining a format beforehand. The intent-driven capture mechanism accepts natural requests and automatically pins the correct type by keywords before writing to the knowledge store.

Keyword inference works by analyzing your natural-language intent to automatically pin the entry type, such as a reference or session summary. It then captures the knowhow into a persistent project store without requiring explicit format selection.

You can record decision records, templates, recipes, references, tips, and session summaries in a project knowledge base. The system processes natural-language intent to determine the appropriate type and stores the entry for reuse.

Yes, you need write access to the knowledge capture workflow directory to capture session summaries and project references. This access allows the system to persist entries directly into `.workflow/knowhow/` for future retrieval.