superpower-bootstrap

To enforce skill discovery at the start of every conversation, you can activate a bootstrap precheck mechanism. This establishes a standardized pre-check process to guarantee a skill is checked, announced, and invoked before the system responds or asks clarifying questions.

Conversation guardrails are mandatory pre-checks that prevent responses before skill discovery and clarifications are complete. When applied to codex-cli interactions, they ensure a skill is checked and announced at the start, tracking all progress via update_plan for auditing purposes.

To stop an assistant from responding before checking active skills, you need to apply mandatory pre-checks at the start of interactions. These guardrails ensure consistent behavior by forcing skill discovery and invocation before any response is generated.

No, the conversation bootstrap mechanism requires no dependencies. It operates independently to enforce skill invocation, announce the active skill, and use update_plan to log progress for auditing without needing external components.

You need a precheck for skill invocation to ensure consistent behavior and proper discovery across all interactions. It satisfies operational requirements by introducing mandatory checks that prevent unmonitored responses and log progress for auditing.

Yes, you can use update_plan to audit skill discovery and progress tracking. The bootstrap precheck announces which skill is in use and logs progress via update_plan, ensuring every conversation start is monitored and satisfies operational requirements.