From PACT
Queries PACT Secretary via SendMessage for project context including past decisions, architectural patterns, history, and lessons learned. Useful before decisions or on unfamiliar code.
How this skill is triggered — by the user, by Claude, or both
Slash command
/PACT:request-more-contextThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The PACT Secretary (secretary) is available for the entire session to answer questions about past decisions, architectural patterns, and project history.
The PACT Secretary (secretary) is available for the entire session to answer questions about past decisions, architectural patterns, and project history.
When to use this:
How to request context:
SendMessage(to="secretary",
message="[{your-name}→secretary] Query: {your question}",
summary="Context request: {topic}")
What you'll get back: Summaries of relevant memories with IDs. If you need more detail on a specific memory, ask a follow-up with the memory ID.
What NOT to ask: Implementation advice, code review, or testing strategy — those are other specialists' domains. The secretary provides historical context only.
npx claudepluginhub synaptic-labs-ai/pact-plugin --plugin PACTQueries project memory to recall context, decisions, and history. Use before starting work, investigating unfamiliar code, or asking about past decisions.
Searches stored memories and decisions using MCP tools to answer questions about past learnings, architectural choices, patterns, and project context like 'what testing framework did we decide on?' or 'ESM import issues?'
Searches and injects relevant memories into context before starting work on a task. Use when beginning a new task, switching context, or when project history, past decisions, or coding conventions need to be loaded.