outcomeeng

ALWAYS invoke this skill when diagnosing the health of a spec-tree or spx environment, when checking whether the SessionStart hook fired for the current session, or when troubleshooting a missing session identity, worktree claim, or unreachable spx CLI. NEVER guess why session state is missing without running these checks first.

ALWAYS invoke this skill when diagnosing the health of a spec-tree or spx environment, when checking whether the SessionStart hook fired for the current session, or when troubleshooting a missing session identity, worktree claim, or unreachable spx CLI. NEVER guess why session state is missing without running these checks first.

ALWAYS invoke this skill when diagnosing the health of a spec-tree or spx environment, when checking whether the SessionStart hook fired for the current session, or when troubleshooting a missing session identity, worktree claim, or unreachable spx CLI. NEVER guess why session state is missing without running these checks first.

ALWAYS invoke this skill when writing or fixing tests for Python. NEVER write or fix Python tests without this skill.

ALWAYS invoke this skill when selecting the next executable slice to implement or deciding which spec-tree nodes /apply should build next from an implementation plan. NEVER choose the next nodes by ad hoc selection — this skill scopes an existing plan to demonstrable value before /apply runs.

ALWAYS invoke this skill when writing or fixing tests for Python. NEVER write or fix Python tests without this skill.

ALWAYS invoke this skill when writing or fixing tests for Python. NEVER write or fix Python tests without this skill.

SKILL.md audit methodology preloaded by the skill-auditor agent. The main conversation reaches this audit only through that agent.

ALWAYS invoke this skill when auditing ADRs for Python or after writing an ADR. NEVER implement from an unaudited ADR.

ALWAYS invoke this skill when auditing code for Python or after writing code. NEVER modify a spec to match code without auditing the code first.

ALWAYS invoke this skill when auditing tests for Python or after writing tests. NEVER use auditing-python for test code.

Python ADR conventions enforced across architect and auditor skills. Loaded by other skills, not invoked directly.

ALWAYS invoke this skill when auditing PDRs or after writing a PDR. NEVER audit PDRs without this skill.

ALWAYS invoke this skill when auditing test evidence quality, after writing tests for a spec node, or before closing an outcome.

ALWAYS invoke this skill when auditing ADRs for TypeScript or after writing an ADR. NEVER implement from an unaudited ADR.

ALWAYS invoke this skill when auditing code for TypeScript or after writing code. NEVER modify a spec to match code without auditing the code first.

Subagent-configuration audit methodology preloaded by the subagent-auditor agent. Dispatch subagent-auditor to audit subagent configuration files; the main conversation reaches this audit only through that agent.

ALWAYS invoke this skill when creating, editing, or configuring subagents. NEVER create subagents without this skill.

Skill authoring standards enforced across all creating and auditing skills. Loaded by other skills, not invoked directly.

Agent prompt writing conventions enforced across all creator and auditor skills. Loaded by other skills, not invoked directly.

SKILL.md audit methodology preloaded by the skill-auditor agent. Dispatch skill-auditor to audit SKILL.md files; the main conversation reaches this audit only through that agent.

ALWAYS invoke this skill when creating, editing, or improving SKILL.md files.

ALWAYS invoke this skill when designing or building web components, pages, or dashboards. NEVER design or build web UI without this skill.

ALWAYS invoke this skill when writing reader-facing documents such as public docs, web pages, and product messages for outside readers like developers and customers. NEVER invoke for chat responses to the user (no matter how long), operational prose like code comments, commit messages, or agent-facing instructions like SKILL.md.

ALWAYS invoke this skill when projecting a next-methodology target structure, splitting current spec-tree nodes into target kinds, auditing a proposed target tree, deriving migration slices from a projection, or updating coordination notes from reviewed structure views.