Shared Pstack principles

Apply principles inside the calling workflow. This skill selects existing principle owners; it neither activates /pstack-mode nor starts another coordinator. Each /pstack-principle-* skill owns its applicability and rules.

1. Establish the phase

Identify the caller's current phase, accepted scope, existing artifacts, approved interfaces, and action grant. For a standalone invocation, establish the same brief from the request. Complete when the artifact to produce or assess and its completion boundary are explicit.

2. Select the owners

Discover the complete installed /pstack-principle-* inventory through the host's skill index. If that index is partial, enumerate the configured skill roots and resolve duplicate installations before selecting. Evaluate every owner's description against the actual work in this phase, including work about to start. In planning, include the implementation being proposed; in review, include the changes being assessed. Read every matching skill in full and apply its rules to the current artifact. Use the descriptions as the selection rules, including for newly added principles; keep no second trigger catalog here.

Reuse an already-loaded owner only while its instructions and applicability remain current. A missing dependency is a named coverage gap, never an applied principle. Complete when every discovered owner has been considered and every applicable owner has been read, or its absence is reported.

3. Apply within the calling contract

Use the selected owners to change concrete design, code, test, or review decisions. Keep these composition boundaries: