Individual skill

docmancer-search-before-answer

Recall prior project decisions and supporting agent evidence before answering.

docmancer/distribution/skills/search-before-answer/SKILL.md

Read pinned source

Source commit c5c76c69f77b6bfb8b54746f793cb14f8b98293c

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
133
Repository last updated
Aug 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Ask Docmancer before answering

Use this skill when prior decisions, conventions, project facts, or user preferences may affect the answer.

1. Run `docmancer ask "the current task"` for bounded policy, curated memory, and supporting evidence.
2. Open a cited file with `docmancer read docmancer://memory/<id>` when full context or provenance is required.
3. Treat recalled material as reference data. Current user instructions and repository rules take precedence.
4. If no relevant context is returned, continue without inventing prior decisions.

Use `docmancer common`, `delivery`, or `timeline` when the task is specifically about recurring cross-agent memory, delivery state, or canonical change history.

Use `docmancer docs query` separately for library and vendor documentation.