ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified

backstage

Manage backstage workflow in projects (ROADMAP, checks/, CHANGELOG). Triggers: 'backstage start', 'vamos trabalhar no X', 'backstage health'. Installs protocol if missing, updates global rules, runs health checks, shows active epics. Use for: epic planning, project setup, quality enforcement, context switching.

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/nonlinear/backstage
Or

Backstage Skill

Nickname: backstage:

Objective: Universal project status management for AI-assisted development. Ensures documentation matches reality before every commit.


🔴 Why This Skill Exists (Anti-Drift)

Backstage-skill = ANTI-DRIFT:

  • ✅ Force context awareness (project/epic)
  • ✅ Health checks prevent chaos
  • ✅ Architecture-first workflow
  • ✅ Roadmap visibility = no surprises

WITHOUT IT:
Work happens outside backstage → drift → broken trust → triple metabolic cost

WITH IT:
"good morning X" → automatic context load → work inside boundaries → paridade maintained


The Metabolic Cost Problem:

Without backstage, delegation costs triple:

  1. The work itself
  2. Explicating methodology (ethics, preferences, protocols)
  3. Defining WHERE that learning gets stored (VISION? SOUL? SKILL? memory?)

This is exhausting for the human.

Investment is worth it ONLY IF plateau is reached:

  • Human teaches ONCE → AI internalizes
  • Each session: READ context files → act according to ethics
  • Each session: LESS explanation needed
  • Plateau = Human delegates, AI executes without supervision

This skill enforces stabilization.
Force context awareness (project/epic/design architecture) to prevent drift.
3x work becomes 1x work.


Policies & Checks Enforcement

Backstage-skill enforces ALL rules in checks/ (deterministic + interpretive, global + local).

Enforcement Model

flowchart TD
    READ_CHK["Read checks/<br/>global + local<br/>[Deterministic .sh + Interpretive .md]"]
    
    CONFLICT{Conflict?}
    MERGE[Merge compatible rules]
    LOCAL[Local wins]
    
    AI["AI interprets .md checks<br/>[Contextual enforcement]"]
    SH["Bash executes .sh checks<br/>[Deterministic validation]"]
    
    AI_ACT[✅ Enforce or discuss]
    AI_AMBIG[⚠️ Ask user]
    
    SH_OK[✅ All checks pass]
    SH_FAIL[❌ Checks failed]
    
    REPORT["Report:<br/>📋 Interpretive (always ✅)<br/>🔍 Deterministic (✅/❌)"]
    
    READ_CHK --> CONFLICT
    CONFLICT -->|No| MERGE
    CONFLICT -->|Yes| LOCAL
    MERGE --> AI
    MERGE --> SH
    LOCAL --> AI
    LOCAL --> SH
    
    AI -->|Clear| AI_ACT
    AI -->|Ambiguous| AI_AMBIG
    
    SH -->|Pass| SH_OK
    SH -->|Fail| SH_FAIL
    
    AI_ACT --> REPORT
    AI_AMBIG --> REPORT
    SH_OK --> REPORT
    SH_FAIL --> REPORT

Two enforcement domains:

  1. Checks (Interpretive)

    • checks/global/*.md = Universal workflow rules
    • checks/local/*.md = Project-specific overrides
    • Enforced by: AI (reads markdown, interprets context, acts)
    • Always pass: AI reads, understands, will act accordingly
  2. Checks (Deterministic)

    • checks/global/*.sh = Universal validation tests
    • checks/local/*.sh = Project-specific tests
    • Enforced by: Bash (executes shell scripts, exit codes)
    • Pass or fail: ✅ (exit 0) or ❌ (exit non-zero)

Metadata

Author@nonlinear
Stars1287
Views0
Updated2026-02-22
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-nonlinear-backstage": {
      "enabled": true,
      "auto_update": true
    }
  }
}
Safety NoteClawKit audits metadata but not runtime behavior. Use with caution.