doc

To persist mid-work decisions, this Skill captures design rationale and findings, then routes them to appropriate files like MEMORY.md or architecture docs. It identifies information types, checks existing files for novelty, and writes new content to prevent loss during active development cycles.

The best way to save reasoning chains is using automated mid-work documentation. This Skill classifies emerging conventions and logic, checks for duplicates against existing project files, and securely logs the rationale to snapshot files before context compression occurs.

You can automatically route captured knowledge by leveraging a built-in decision tree. This mechanism evaluates mid-work findings, determines the correct target file such as architecture docs or MEMORY.md, and ensures documentation practices are maintained without manual sorting.

Yes, this documentation tool performs a novelty check before writing. It scans target files within your project directory to verify if the decision or finding already exists, preventing duplication and ensuring only new insights are persisted to your architecture docs.

You need mid-work documentation during active development sessions when complex decisions emerge. It prevents valuable insights, design choices, and reasoning from being forgotten or lost when context is compressed, ensuring project knowledge remains accessible.

Yes, you can use this to save finalized design decisions to architecture documentation. After a complex discussion, the Skill captures the rationale and routes it directly to the appropriate project files, maintaining accurate knowledge management throughout development.