boundary-bbcr-fallback
Execute automatic BBCR (Collapse-Rebirth Correction) when knowledge boundaries are exceeded or reasoning fails.
A simple, powerful system that helps you organize and track your development work. Think of it as your personal project assistant that breaks down big ideas into manageable tasks and keeps everything organized.
$ npx -y skills add qdhenry/Claude-Command-Suite --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
/ORCHESTRATION-READMEContext preview
What this command does when you run it.
A simple, powerful system that helps you organize and track your development work. Think of it as your personal project assistant that breaks down big ideas into manageable tasks and keeps everything organized.
A simple, powerful system that helps you organize and track your development work. Think of it as your personal project assistant that breaks down big ideas into manageable tasks and keeps everything organized.
Imagine you have a big project like "build a user login system." This tool:
Simply tell the system what you want to build:
/orchestration/start I need to build a user authentication system with: - Login and logout - Password reset via email - Remember me functionality - Social media login (Google and Facebook)
The system will: 1. Ask clarifying questions if needed 2. Create organized task files 3. Set up a tracking system 4. Give you a clear plan to follow
See what's happening at any time:
/orchestration/status
This shows you:
Left for lunch? Changed computers? No problem:
/orchestration/resume
This brings back everything:
Here are the main commands you'll use:
| Command | What it does | When to use it | |---------|--------------|----------------| | `/orchestration/start` | Begin a new project | Starting fresh work | | `/orchestration/status` | Check progress | See what's happening | | `/orchestration/resume` | Continue working | After any break | | `/orchestration/move` | Update task status | When you complete something | | `/orchestration/commit` | Save to Git | When code is ready |
/orchestration/resume > You have 3 active projects: > 1. authentication_system (65% done) > 2. payment_processing (40% done) > 3. admin_dashboard (85% done) > > Which one? [1]
When you complete something:
/orchestration/move TASK-003 qa > Moving "Add login form" to testing > Ready to commit your changes? [Y/n]
The system helps you make professional commits:
/orchestration/commit > Creating commit for TASK-003: Add login form > Generated message: > "feat(auth): implement user login form > > - Add email/password fields > - Include validation > - Add remember me checkbox > > Task: TASK-003"
Your tasks are organized like a filing cabinet:
π **todos/** - Tasks ready to start π **in_progress/** - What you're working on now π **qa/** - Finished but needs testing π **completed/** - All done! π **on_hold/** - Waiting for something
/orchestration/start Paste your requirements or describe what you want to build
/orchestration/status # See everything /orchestration/status --today # Just today's work
/orchestration/resume # List all projects /orchestration/resume --latest # Jump to most recent
/orchestration/move TASK-001 in_progress # Start working /orchestration/move TASK-001 qa # Ready for testing /orchestration/move TASK-001 completed # All done!
/orchestration/commit # Commit current task /orchestration/commit TASK-003 # Commit specific task
/orchestration/find "login" # Find tasks about login /orchestration/find --ready # Find tasks ready to start
/orchestration/report standup # Daily standup format /orchestration/report executive # High-level overview
/orchestration/sync # Update task status from commits /orchestration/sync --check # See what's out of sync
/orchestration/remove TASK-005 # Remove unwanted task /orchestration/remove TASK-005 --archive # Keep a backup
1. /orchestration/resume # See what you were doing 2. /orchestration/status --today # Check today's priorities 3. Pick a task and start working!
1. Finish your code 2. /orchestration/move TASK-003 qa # Mark as ready for testing 3. /orchestration/commit # Save to Git 4. Move on to the next task!
1. /orchestration/commit # Commit any pending work 2. /orchestration/status # See overall progress 3. /orchestration/sync # Make sure Git is in sync
The system creates a special folder structure:
π task-orchestration/
π 03_15_2024/ # Today's date
π authentication_system/ # Your project
π MASTEA comprehensive development toolkit designed following Anthropic's Claude Code Best Practices for AI-assisted software development.
Repo: qdhenry/Claude-Command-Suite
Execute automatic BBCR (Collapse-Rebirth Correction) when knowledge boundaries are exceeded or reasoning fails.
Analyze semantic position relative to knowledge boundaries to prevent hallucination and identify uncertainty zones.
Generate a visual heatmap of knowledge boundaries showing safe zones, risk areas, and semantic coverage.
Evaluate the current risk level and provide detailed analysis of potential hallucination or reasoning failure.
Find and construct semantic bridges to safely navigate from current position to target concept without crossing dangerous boundaries.
Takes an input prompt and returns ONLY a token-optimized version that preserves meaning while minimizing token count. Based on LLM tokenization principles:β¦