wagner-protocol-enforce

Enforce the Wagner 12-rule protocol during oimpresso coding sessions.

Updated May 14, 2024
One-click install
npx skills add https://github.com/wagnerra23/oimpresso.com --skill wagner-protocol-enforce
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wagner-protocol-enforce
Source: https://github.com/wagnerra23/oimpresso.com/tree/main/.claude/skills/wagner-protocol-enforce
Command: npx skills add https://github.com/wagnerra23/oimpresso.com --skill wagner-protocol-enforce

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents missed governance, safety, and workflow requirements by ensuring Claude follows the same 12 behavioral rules every time, without Wagner having to repeat them.

Core Features & Use Cases

  • Always-on protocol loading: Ensures the canonical behavior protocol (PROTOCOLO-WAGNER-SEMPRE.md) is available at session start so rules are consistently applied.
  • Auto-execution of triggered rules: Performs required actions when triggers occur (e.g., smoke-real evidence after deploy, literal copy when design is approved, 3-phase workflow for module edits).
  • Hard guardrails for multi-tenant and memory discipline: Reinforces Tier 0 multi-tenant safety and blocks private auto-memory writes.
  • Human approval gate: Requires human approval before commit/push/merge operations when Rule R10 triggers.

Quick Start

Use the wagner-protocol-enforce skill to run your next oimpresso change session and have Claude automatically load and apply the Wagner 12-rule protocol.

Frequently Asked Questions about wagner-protocol-enforce

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce consistent governance and workflow rules automatically during Claude sessions?

To enforce governance rules during Claude sessions, use a prompt protocol skill that loads behavioral guidelines at session start and automatically executes triggered actions like smoke testing and human approval gates to maintain workflow discipline.

What is multi-tenant safety in workflow enforcement and when do I need it?

Multi-tenant safety in workflow enforcement prevents data cross-contamination across tenants during coding or review tasks. You need it when editing modules or preparing deploy actions to ensure Tier 0 safety guardrails are consistently applied without manual repetition.

How do I require human approval before git commit, push, and merge operations?

To require human approval before git operations, implement a governance protocol that triggers an approval gate when commit, push, or merge actions are detected, ensuring a human operator explicitly authorizes the action before execution.

Can I use prompt protocol enforcement for both human-driven and agent-driven coding tasks?

Yes, prompt protocol enforcement applies to both human-driven and agent-driven coding or review tasks. It ensures the same behavioral rules are executed consistently regardless of whether a human or an agent is initiating the session.

How do I prevent private auto-memory writes during automated coding sessions?

To prevent private auto-memory writes during automated sessions, apply hard guardrails within your prompt protocol that explicitly block unauthorized memory write operations, ensuring session data discipline and multi-tenant safety.

Does workflow enforcement require smoke testing evidence after deployment?

Yes, workflow enforcement requires smoke-real evidence after deployment. The protocol automatically triggers this verification step to ensure functional stability before considering a deploy action fully complete.