// Wire new rules, policies, and behavioral constraints into the correct governance file with an explicit enforcement assessment.
Maintain the live agent context surface: bootstrap hygiene, memory routing, conversation continuity, and context-health monitoring.
Validate, audit, and maintain scheduled agent automation without unsafe direct state edits.
Plan-first workflow for non-trivial work: define the goal, create or reuse a tracker issue, package context, execute on an issue-named branch when code changes, and verify completion with evidence.
jarvOS personal AI operating system — project management, ontology alignment, governance, and behavioral rules for your assistant.
| name | rule-creation |
| description | Wire new rules, policies, and behavioral constraints into the correct governance file with an explicit enforcement assessment. |
| triggers | ["make a rule","add this rule","from now on","formalize that","new policy","rule-creation"] |
| metadata | {"jarvos":{"bundle":"operating-system-skills","portability":"generic"}} |
Use this skill when a user declares, proposes, or asks to formalize a behavioral rule. Do not leave the rule as a chat promise. Wire it into the system of record, then report what changed.
The workflow is complete only when:
## Rule Name (HARD|soft)
Plain-language requirement.
**Enforced by:** `path/to/workflow-or-script` (when applicable)
| Rule type | Typical destination |
|---|---|
| Always-loaded behavior | AGENTS.md or equivalent root instructions |
| Tool/CLI policy | TOOLS.md or equivalent tooling guide |
| Non-negotiable safety | CRITICAL-RULES.md or root instructions |
| Persona/voice | SOUL.md, IDENTITY.md, or persona docs |
| Project-only rule | Project issue, project brief, or project docs |
Create enforcement when any condition is true:
Choose the lightest effective mechanism:
Rule wired: <name>
Location: <file>
Type: HARD|soft
Enforcement: <workflow/script/tool restriction/doc-only/unavailable>