| name | using-pandastack |
| description | Use at the start of any session — establishes the cognitive contract that pandastack skills must be checked BEFORE any response or action, including clarifying questions. |
If you were dispatched as a subagent to execute a specific task, skip this skill.
If you think there is even a 1% chance a pandastack skill might apply to what the user is about to do, you MUST invoke the skill via the `Skill` tool before responding.
This is not negotiable. Skills override default behavior. Rationalizing your way out of a skill check is the failure mode this contract exists to prevent.
Why this file exists
pandastack ships ~37 skills, 5 personas, 7 lifecycle flows. The surface area is too large for ad-hoc invocation. Without a forcing function, the model defaults to "I'll just answer directly" and the skills never run. This file is the forcing function.
The failure mode this exists to prevent (observed across many sessions): writing code without running careful for prod paths, shipping without review, finishing a knowledge note without knowledge-ship. The skills exist; they just don't get invoked unless something pressures the check.
Instruction priority
- User's explicit instruction (this turn's message, project CLAUDE.md / AGENTS.md) — highest
- pandastack skill content — overrides default behavior when relevant
- Default Claude Code behavior — lowest
If the user says "skip the review, just commit", do that. The contract is not a tyrant.
Lifecycle → skill map
When the current task matches one of these signals, the corresponding skill must be checked:
| Signal | First skills to check |
|---|
| About to write/edit code in any production / shared-infra path | pandastack:careful (gate), then dev flow |
| Bug fix / feature / refactor (3+ files OR new abstraction) | pandastack:grill or /plan first, NOT direct edits |
| About to commit | pandastack:review first, THEN pandastack:ship |
Finished a knowledge note (knowledge/<domain>/<note>.md style) | pandastack:knowledge-ship to Close + Extract + Backflow |
Finished a draft ready to publish (Obsidian Blog/_daily/ or equivalent) | pandastack:write-ship |
| Finished a work topic with a decision to log | pandastack:work-ship |
| Researching an unfamiliar concept | pandastack:grill (adversarial) → pandastack:deep-research |
| Weekly / monthly retrospective time | pandastack:retro-week / pandastack:retro-month |
| Don't know which skill | Read RESOLVER.md at pandastack repo root |
When a skill applies, announce: "Using pandastack:<skill> to " — then invoke the Skill tool. Do not read SKILL.md files directly with the Read tool.
Red flags (rationalizations to STOP on)
These thoughts mean you are about to skip a skill that applies. Stop and check.
| Thought | Reality |
|---|
| "This is just a small change" | Small changes are how prod gets broken. Run careful if it touches a prod path. |
| "I'll just answer directly" | Questions are tasks. The skill might tell you a better way to answer. |
| "The user probably knows what they want" | The user set up these skills because default behavior drifts. Trust the contract. |
| "I'll do the skill check after I look at the code" | Skill check is BEFORE exploration. Skills tell you HOW to explore. |
| "It's just a typo / rename" | Then it takes 10 seconds. Run it. |
| "Running review/ship feels like overkill" | The skill itself decides if it's overkill. Invoke it and let it short-circuit. |
| "I'll bundle the learning extract for later" | Later = never. knowledge-ship Stage 2 is the contract. |
| "I'll skip ship-log, the commit message captures it" | Ship logs aggregate; commit messages do not. |
| "I remember what knowledge-ship does" | Skills evolve. Read the current version via the Skill tool. |
| "The user said 'just do X'" | "Just do X" is WHAT, not HOW. Skills handle HOW. |
| "This is meta / harness work, not real work" | Harness work goes through the same gates. Especially careful on shared config. |
| "There's no exact match" | Pick the closest. Mismatch is fine; skipped check is not. |
When NOT to invoke
- Reading code or files for orientation only (no edits planned)
- One-line answer to a factual question that does not trigger any lifecycle
- Subagent context (handled by
<SUBAGENT-STOP> above)
- User explicitly says "skip skills this turn" or "just do X, no skill"
Overlay extension
A personal / org overlay may be appended to this contract by the SessionStart hook (default search path: ${PANDASTACK_OVERLAY} env var, falling back to $HOME/site/skills/pandastack-private/overlays/using-pandastack.md).
The overlay typically adds:
- Concrete vault / repo / memory paths bound to abstract slots above
- Private skill triggers (org-specific alerts, internal SOPs)
- Active dogfood / experiment windows
If the overlay is missing, this public contract still works on its own — the lifecycle map degrades to abstract guidance.
