home / skills / ladderchaos / tora-skills / process-rules

process-rules skill

safe

This skill helps you maintain governance of processes by creating workflows, documenting lessons, proposing changes, and auditing consistency.

npx playbooks add skill ladderchaos/tora-skills --skill process-rules

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.0 KB

---
name: process-rules
description: Standard Operating Procedures manager - owns all process, rule, and workflow changes. Use this skill when adding workflows, recording lessons learned, proposing rule changes, or auditing process consistency.
---

# Process Rules

Single authority for changes to processes, rules, and workflows.

## When This Skill Activates

- Adding a new workflow
- Recording a mistake/lesson
- Updating process documentation
- Proposing new rules
- After sessions with repeated errors
- Process consistency audits

## Scope

This skill exclusively owns:
- Workflow definitions
- Lessons learned documentation
- Process guides and references
- Rule proposals

## Responsibilities

### 1. Create/Edit Workflows
- Check existing workflows for conflicts
- Follow standard templates
- Update guides if adding new workflow

### 2. Record Lessons Learned
When a mistake is identified:
```markdown
## Lesson: [Title]
- **Date**: YYYY-MM-DD
- **Mistake**: What went wrong
- **Symptom**: How it manifested
- **Fix**: How to prevent it
- **Rule**: (Optional) Proposed rule
```

### 3. Propose Rule Changes
For rules that should apply automatically:
1. Draft the rule text
2. Present to user for approval
3. User applies in settings

### 4. Audit Consistency
Periodically check:
- Workflows don't contradict each other
- Guides match actual workflows
- Lessons learned is up to date

## Change Log Protocol

When making changes:
```markdown
## SOP Change - [DATE]
- **What**: [Description of change]
- **Why**: [Rationale]
- **Files**: [List of files modified]
```

## Anti-Patterns

- Editing workflows without proper review
- Adding lessons without date/context
- Creating overlapping workflows
- Proposing rules without user approval

## Files Under Management

| File Type | Purpose |
|-----------|---------|
| `workflows/*.md` | Role and process definitions |
| `LESSONS_LEARNED.md` | Persistent mistake memory |
| `GUIDE.md` | Quick reference |
| `pre-commit hooks` | Automated checks |

Overview

This skill manages Standard Operating Procedures, owning all process, rule, and workflow changes. It centralizes workflow definitions, lessons learned, and rule proposals to keep operations consistent and auditable.

How this skill works

When you add or change a workflow, record a mistake, or propose a rule, this skill verifies existing workflows for conflicts, applies standard templates, and updates related guides. It records lessons with date, symptom, fix, and optional rule proposals, and it provides a structured change-log entry for every SOP update.

When to use it

Adding a new workflow or role-based process
Recording a mistake or documenting a lesson learned
Proposing or updating operational rules
Auditing processes for consistency and contradictions
After repeated errors or incident review sessions

Best practices

Always check existing workflows for overlap before creating a new one
Use the standard templates for workflows and lesson entries
Include dates and context on every lesson or change-log entry
Present proposed rules to the user for explicit approval before applying
Run periodic audits to ensure guides match actual workflows

Example use cases

Add a new deployment workflow and update the quick reference guide
Record a post-incident lesson with symptom, fix, and optional rule to prevent recurrence
Propose an automated rule for a setting and present it for user approval
Audit all workflows to resolve contradictions and update the change log
Add pre-commit hook changes to enforce new process checks

FAQ

What format should lessons learned use?

Use the provided template with Title, Date, Mistake, Symptom, Fix, and optional Rule for consistency and traceability.

Who approves proposed rule changes?

The user must review and explicitly approve proposed rules before they are applied to settings or automation.