Context Research
During the analysis phase of any development workflow, KnowzCode automatically queries your Knowz vaults for relevant context. Past architectural decisions, known gotchas, related patterns, and previous implementations inform the specification phase, preventing repeated mistakes and ensuring consistency.
How it works
When a new /knowzcode:work task starts, the Context Scout and Knowledge Liaison agents search your vaults in parallel with the Analyst's code review. They look for: past decisions related to the affected components, known issues with similar changes, patterns used in related features, and any relevant conventions or standards. This context is included in the briefing that the Architect receives, ensuring the specification builds on existing knowledge rather than starting fresh.
Analysis phase showing vault context alongside code analysis
Screenshot coming soon
Why it matters
Without knowledge integration, every AI session is amnesic. The AI might propose a solution your team already tried and rejected. It might violate a convention documented three months ago. Context research prevents these problems by making the full history of your project's decisions available during planning. The result is specifications that are informed by experience, not just code analysis.
Specification enriched with relevant past decisions from vault
Screenshot coming soon
Related Features
Knowledge Liaison
Connects to Knowz vaults: searches past decisions during planning, captures learnings after completion.
Context Scout
Researches project history: scans existing specs, past work, and related context.
Search Knowledge
Semantic search across vaults by meaning, with filters for vault, tags, date, and type.