peri: Skill for Claude Code

Consulting the Advisor

Use a tool-free Opus advisor to improve a decision, not to outsource exploration or execution. The main agent remains responsible for repository inspection, scope, security, implementation, verification, and the final decision.

Trigger decision

For an extreme-risk decision, the main agent may collect the advisor's requested minimum evidence and consult again. Do not loop merely to seek agreement.

Prepare the decision packet

Before dispatching .claude/agents/advisor.md, inspect the relevant code, tests, contracts, and current diff. Send only the smallest packet that lets a tool-free advisor reason correctly:

# Advisor Decision Packet

## Task contract
- Goal:
- Success criteria:
- In scope / out of scope:
- Constraints, deadline, and risk:

## Evidence
- Code facts: `path:symbol` plus necessary excerpts.
- Tests, errors, command results, and current behavior:
- Affected interfaces, consumers, or compatibility requirements:

## Reasoning so far
- Candidate options:
- Attempts and their outcomes:
- Open questions and assumptions:

## Decision requested
- Exact choice or trade-off the advisor must evaluate:

Facts must include a source path, test name, command output, or another traceable origin. Label interpretations as assumptions. Before dispatch, scan the packet for secrets and sensitive material: credential-like assignments (KEY, TOKEN, SECRET, PASSWORD), authorization headers, cookies, PEM blocks, connection strings, complete environment dumps, raw traces, and unbounded stderr. If found, do not dispatch the packet; replace it with the smallest redacted or structural evidence needed for the decision. Never include secrets, tokens, passwords, connection strings, unredacted environment values, or unnecessary personal data.