aget-study-topic

To research existing knowledge base patterns before starting a new project, run a focused topic study that searches across L-docs, SOPs, and governance artifacts. This returns an evidence-based summary of matched entries, relevant constraints, and recommended next steps to prevent duplicated implementation work.

The best way to discover requirements and governance constraints is to perform read-only searches across designated knowledge base areas. This surfaces active project plans and matching governance rules, returning an objective findings summary with coverage-based recommendations for what to read next.

You find relevant L-docs and project plans by executing a targeted knowledge base research command for your specified topic. It scans designated repository sections and provides a structured results summary detailing document counts, matched patterns, and actionable next-step recommendations.

Yes, you can check active plans and SOPs without modifying the knowledge base because this research process performs strictly read-only searches. It safely queries designated KB areas to locate relevant artifacts and returns an evidence-based summary without writing changes or altering existing governance constraints.

Your implementation duplicates existing work because it lacks prior knowledge base research to identify reusable patterns and active plans. Conducting focused topic research before proposing changes reduces uncertainty, surfaces relevant SOPs, and ensures your implementation aligns with established governance constraints.

You need to run a knowledge base topic study before proposing changes whenever you are starting new implementation work or building new features. It checks for existing patterns, active project plans, and governance constraints, ensuring your proposed changes are evidence-based and prevent weak implementation choices.