Skills do not choose the workflow
A skill gives an agent focused instructions for a particular kind of work. That is useful when the task is clear. A real engineering request often needs several steps: inspect the system, choose a design, implement it, and verify the result. Someone still has to choose those steps and put them in order.
When I wire skills by hand, I make that routing decision in every prompt. I decide which instructions apply, when to call them, and what evidence should close the task. The choices are easy to miss and hard for a team to review because they live in one-off requests.
Route the request to a playbook
pstack gives that routing job to its main entry point, /poteto-mode. It reads the request and selects a playbook that fits the work, such as a bug fix, feature, or investigation. The playbook defines the sequence and calls on focused skills as its steps need them.
A bug fix, for example, should establish the failure before changing code, trace the cause, make a repair, and verify the behavior. That sequence belongs in the playbook. A specialized skill can guide one step without carrying the whole task lifecycle in its own instructions.
The plugin packages the working parts
pstack is a plugin because it groups more than one skill. It ships the routing entry point alongside playbooks, focused skills, shared principles, agent roles, setup guidance, and supporting documentation. Each part has a narrower job, while the plugin gives the team one package to install and maintain.
That package changes the unit of reuse. Instead of sharing a folder of disconnected prompts and asking every engineer to compose them, a team can share a workflow with its entry point and supporting pieces together. The pieces stay small, but the path between them becomes visible.
Keep routing separate from orchestration
The router selects the playbook. It does not become the external process that executes the work. The agent host runs the selected instructions, uses its tools, and handles any requested delegation. The plugin supplies the playbook and the agent role that the host can call.
This distinction helps keep roles clear. An Architect skill can help shape an interface or plan a change. It does not orchestrate the work by itself. The host process owns execution and delegation, while the playbook describes when those actions fit into the task.
Make the workflow operable by a team
Routing skills through playbooks gives a team a shared starting point. Engineers can see how a request is classified, which steps follow, and where verification happens. Leads can review a workflow as an operating practice rather than infer it from a collection of prompts.
A plugin does not guarantee good results. Teams still need clear playbooks, maintained skills, human review where the work calls for it, and evidence that the result meets the request. I use pstack because it makes those decisions easier to inspect and improve than wiring the same skills from scratch for each task.