executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
authority-credibilityUse when presenting or auditing expertise, credentials, certifications, advisory boards, expert quotes, trust badges, medical claims, legal claims, financial claims, institutional logos, titles, uniforms, or authority signals that could create undue deference.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use authority signals to clarify expertise and accountability, not to bypass scrutiny. Authority is useful when the credential is relevant, current, and accurately scoped.
guidelines.md to choose the smallest useful reference set.references/authority/knowledge.md for concepts and references/authority/rules.md for operating rules.workflows/verify-credibility-signals.md for repeatable tasks.| File | Purpose |
|---|---|
| references/authority/knowledge.md | Core concepts and source-grounded definitions |
| references/authority/rules.md | Rules, boundaries, and practical guidelines |
| references/authority/examples.md | Bad/better examples for applied situations |
| references/authority/smells.md | Red flags and anti-patterns to detect |
| references/authority/checklist.md | Fast review checklist |
| workflows/verify-credibility-signals.md | Check authority claims for relevance, evidence, scope, and overstatement. |
Use the prompts in evals/evals.json as smoke tests. A good result identifies the relevant Influence principle, preserves user agency, and avoids fabricated evidence or coercive pressure.