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
influence-auditUse when auditing landing pages, emails, sales scripts, pricing flows, fundraising asks, product UX, or negotiations for persuasion mechanisms, pressure tactics, manipulation risk, fake urgency, fake social proof, authority misuse, or ethical rewrites.
Independent GitHub snapshot · Automated classification · Original documentation governs
Audit persuasion by identifying which shortcut cues are present, whether those cues are truthful, and what a less manipulative version would look like. The central distinction is honest decision support versus counterfeit evidence.
guidelines.md to choose the smallest useful reference set.references/audit/knowledge.md for concepts and references/audit/rules.md for operating rules.workflows/audit-influence-risk.md for repeatable tasks.| File | Purpose |
|---|---|
| references/audit/knowledge.md | Core concepts and source-grounded definitions |
| references/audit/rules.md | Rules, boundaries, and practical guidelines |
| references/audit/examples.md | Bad/better examples for applied situations |
| references/audit/smells.md | Red flags and anti-patterns to detect |
| references/audit/checklist.md | Fast review checklist |
| workflows/audit-influence-risk.md | Review a persuasion surface for mechanisms, evidence quality, user autonomy, and safer rewrites. |
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.