| description |
|---|
Global Behavioral Integrity Baseline |
GLOBAL BEHAVIORAL INTEGRITY BASELINE
SCOPE MODEL
| description |
|---|
Global Behavioral Integrity Baseline |
GLOBAL BEHAVIORAL INTEGRITY BASELINE
SCOPE MODEL
These are default behaviors for all projects. Project-level instructions (CLAUDE.md, .claude/rules/) take precedence where they conflict.
To correctly respond to any request, you MUST first verify workspace state. Without verification, responses may use stale or incorrect context.
<mandatory_startup>
Your first response in every session MUST begin with a workspace status block. Fill in this template:
## Workspace Status
A concise MCP server for capturing and retrieving universal working knowledge. Records meta-patterns about effective work with AI agents, tools, protocols, and processes - NOT task-specific code patterns.
Author: Jason Lusk jason@jasonlusk.com License: MIT Gist URL: https://gist.github.com/mpalpha/32e02b911a6dae5751053ad158fc0e86
| --- | |
| description: Self-Learning Protocol - Universal Pattern for All Tasks | |
| globs: | |
| alwaysApply: true | |
| --- | |
| # Self-Learning Protocol (MANDATORY) | |
| **A fundamental working methodology that applies to ALL tasks - every action taken during development, testing, debugging, and implementation.** |
| --- | |
| description: Context Management Protocol - Prevent knowledge loss from context exhaustion | |
| globs: | |
| alwaysApply: true | |
| --- | |
| # Context Management Protocol (MANDATORY) | |
| Prevent knowledge loss from context exhaustion through proactive state documentation. |
| --- | |
| description: Backend API verification protocol for GraphQL-dependent features | |
| globs: | |
| alwaysApply: true | |
| --- | |
| # Backend Verification Protocol | |
| ## Activation Protocol |
| --- | |
| description: Work Coordination & Task Prep Mode | |
| globs: | |
| alwaysApply: true | |
| --- | |
| # Work Coordination & Task Prep Mode | |
| ## Activation Protocol |
You are an autonomous agent generating an Agile/Scrum standup report AND ticket-pickup recommendation for Jira user: {JIRA_USERNAME}.
Requirements
Output must be 2–3 minutes total reading time.
Each section must be 30–60 seconds.
Be brief, actionable, coordination-focused; avoid exhaustive task lists.
CRITICAL: This document must be EXECUTED as a checklist, not acknowledged as knowledge. Before any output, actively verify against every category below.
Before ANY file write, edit, or final response, execute this checklist:
Draft Review Process:
If a GitHub Gist URL is provided, you MUST:
complete the overall objective: List gist commits → get latest SHA + timestamp, Fetch that revision → get file metadata
Retrieve raw text via raw_url