Pstack mode

Activate this mode for the current conversation when the user explicitly invokes it. Match each new task to the playbooks below. Direct helper invocation does not activate the whole mode. Follow the invoking repository's conventions and the host's actual tools.

Run a task

1. Invoke /domain-modeling to resolve and read the project's shared artifacts. Reuse the existing spec, ticket graph, glossary, domain model, and ADRs as their source of truth. State the goal, scope, and observable done predicate. Identify the data shape and current implementation before changing code. Invoke /pstack-how for unfamiliar architecture and /pstack-why when existing rationale constrains the change. Complete when the brief names the behavior to prove and the relevant boundaries.
2. Read the matching playbook from playbooks/ in this skill directory. Copy its steps into the task list, retaining a skipped step with its reason. Use /pstack-figure-it-out for a large bespoke run; a standing multi-day program uses Orchestrate. Complete when one execution path and its checks are explicit.
3. Invoke the workflow skills needed by that path and /pstack-principles for shared principle selection in the current phase. Use /pstack-swarm for host execution, native delegation, independent review, isolation, and fallback behavior. Helpers own their references; resolve their installed paths through the host's skill index. Complete when every delegate has its scope, applicable principle instructions, evidence contract, and permitted side effects.
4. Execute within the agreed scope. Proceed on reversible implementation work; pause when scope or an approved interface changes, or repeated failures require the user's decision. Explicit merge, deployment, or messaging authorization remains specific to that action. Complete when each unit is proved or its blocker is recorded.
5. Reconcile accepted domain changes through /domain-modeling; canonical docs are edited by the coordinator. Verify against the real artifact, inspect delegated changes, and report the evidence, gaps, and decisions that need attention. Draft pull requests are the default. A missing check never becomes a pass. Complete when the done predicate is demonstrated or the exact unfinished work is reported.

Routing