aget-study-up

To search a knowledge base for existing project plans and governance references, use a read-only research script filtered by topic to surface L-docs, patterns, SOPs, and governance files. This validates the topic argument and returns human-readable or JSON outputs to inform next steps.

The best way to avoid duplicating effort when drafting L-docs is to research the repository knowledge base first. By performing targeted read-only searches filtered by topic, you can surface existing patterns and precedents to ensure new documentation does not overlap with prior work.

Yes, you can assess governance impact across repository directories before making code changes. By searching the knowledge base for topic-specific governance references and SOPs, the script produces a coverage-based recommendation that highlights potential impacts and required precedents.

The knowledge base research script performs strictly read-only searches. It validates a required topic argument and queries L-docs, patterns, project plans, SOPs, and governance directories without modifying any files, producing structured counts and matched file summaries.

To get structured findings from a topic-based repository search, execute the research script with a specific topic. It summarizes match counts, lists matched files across knowledge base directories, and generates a coverage-based recommendation available in human-readable or JSON formats.

You need to search repository SOPs and patterns before proposing changes when preparing for implementation or reviewing prior work. This research prevents redundant work, surfaces existing context, and ensures proposed changes align with established governance and project planning precedents.