create-atomic-note

To create single-topic notes for a knowledge base, generate documentation with a specific title, summary, context, decision, and consequences, then save it using a structured YAML frontmatter format. This ensures your task summaries are easily ingested.

The best way to organize feature development documentation is to save single-topic notes using a consistent file naming convention and YAML frontmatter. This structure enables easy categorization and ingestion into your knowledge base.

Yes, you need YAML frontmatter for knowledge base ingestion because it facilitates metadata tagging and note categorization. This structured format ensures your single-topic documentation is easily referenced.

You document architectural decisions by creating a single-topic note that includes the title, summary, context, decision, and consequences. Saving this structured documentation to a designated directory prepares it for knowledge base ingestion.

Yes, you can create task summaries without complex setup because the process requires no external dependencies. You simply generate the note content with the required summary fields and save it using the specified file naming convention.