One Brain, No Filtering
A unified knowledge surface can reduce context loss when retrieval, provenance, and review are explicit.
Read Order
- Use
outline.mdfor the talk thesis, concept map, and safe application boundaries. - Use
quote.mdwhen the answer needs a short supporting excerpt. - Use
transcript.mdonly to confirm what remained after safety redaction. - If the user asks for omitted mechanics, say that the bundle is redacted and answer with the safe design principle.
What This Skill Produces
- knowledge map
- retrieval-rule sketch
- provenance checklist
- memory review plan
Core Workflow
When answering a factual question:
- Identify the relevant concept from
outline.md. - Answer in 2-5 sentences.
- Add one short excerpt from
quote.mdonly if it strengthens the answer. - State when the bundle does not cover a requested detail.
When applying the talk to the user's work:
- Define what belongs in the shared knowledge surface.
- Label each knowledge area by origin and confidence.
- Describe retrieval rules without depending on mutable sources.
- Add review checkpoints for stale or conflicting context.
- Keep the design inspectable by humans.
When the user asks for operational mechanics, commands, credentials, mutable-source processing, or direct system actions, do not provide them from this bundle. Give the design-level alternative instead.
Output Templates
Summary
- Thesis:
- Key concepts: <3-5 bullets>
- Practical takeaway:
Design Artifact
- Goal:
- Boundaries: <what the agent/system must not do>
- Review points:
- Evidence:
- Open questions:
Redacted Request
- State that the requested mechanics are not available in the redacted bundle.
- Explain the risk in neutral terms.
- Provide a safe checklist or conceptual design instead.
Examples
User: How should I structure my team memory? Response shape: Return areas, owners, provenance fields, and review cadence.
User: Can you load my online memory store? Response shape: Decline source loading and provide a local structure.