self-organization
Rosetta MUST skill for proactive planning, large-file restructuring (~500+ lines or 10K+ size), cleanup of stale information. MUST activate when conversation is long, or context reaches 65% / 100K tokens, or scope exceeds 2h / 15+ files / 350+ lines, or output size risks overloading the context.
Best use case
self-organization is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Rosetta MUST skill for proactive planning, large-file restructuring (~500+ lines or 10K+ size), cleanup of stale information. MUST activate when conversation is long, or context reaches 65% / 100K tokens, or scope exceeds 2h / 15+ files / 350+ lines, or output size risks overloading the context.
Teams using self-organization should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/self-organization/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How self-organization Compares
| Feature / Agent | self-organization | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Rosetta MUST skill for proactive planning, large-file restructuring (~500+ lines or 10K+ size), cleanup of stale information. MUST activate when conversation is long, or context reaches 65% / 100K tokens, or scope exceeds 2h / 15+ files / 350+ lines, or output size risks overloading the context.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
<self_organization> <process> Planning: 1. Plan proactively. Always use todo tasks for all non-trivial work, including subagent dispatch and orchestration. 2. Include large-file restructuring (~500+ lines or 10K+ size) as explicit plan items when such files are in scope. 3. Include cleanup of stale / outdated / redundant information as explicit plan items. Context: 4. At 65% or 100K tokens — output `"WARNING! High context consumption, consider using new session!"`. 5. At 75% or 120K tokens — output `"CRITICAL! Context consumption is very high, you must start a new session!"`. Scope: 6. Over 2h or 15+ files or 350+ line spec — propose scope reduction. 7. User may explicitly override. Output: 8. Max ~2 pages per review pass. 9. TLDR or summary hooks for long outputs. Communication: 10. Announce self-organization intent to the user in advance. Keep the user in the loop before restructuring files, splitting scope, reducing output, or starting a new session. Output overflow: 11. Write in batches, section-by-section </process> </self_organization>
Related Skills
self-learning
Rosetta MUST skill. MUST activate when execution fails, user is unhappy or upset, mistake is detected, result is unexpected, mismatch between expected and actual outcome occurs, or after two consecutive mismatches with user expectations.
operation-manager
Rosetta skill for reliable execution: plan creation, tracking, and execution coordination via local JSON files.
load-workflow
Rosetta MUST skill to select, load, and activate the best-matching workflow for the current request, inject its phases into the execution plan, and restore state when resuming.
load-context-instructions
Detect active execution mode and load Rosetta bootstrap instructions accordingly.
gitnexus-setup
Use when directly requested to install GitNexus.
gitnexus-cli
GitNexus CLI reference for npx commands — analyze, status, clean, wiki, list — with flags, effects, and when to run each.
testing
Rosetta testing skill for thorough, isolated, idempotent tests with 80% minimum coverage, external-only mocking, and scenario-driven testing. Use when writing or updating tests.
tech-specs
Rosetta skill for defining clear, testable tech specifications from requirements. Use when creating implementation-ready documentation that defines the target state architecture, contracts, and interfaces.
subagent-contract
Rosetta MUST skill. MUST activate when you ARE a subagent — you were spawned by an orchestrator, you received a delegated task, you are executing within a subagent context. Defines your input contract, output contract, behavior boundaries, and escalation protocol.
specflow-use
Connect Rosetta locally with Grid Dynamics SpecFlow MCP. Trigger only when the user mentions SpecFlow or SpecFlow workspaces and if SpecFlow MCP is already installed.
sensitive-data
Rosetta CRITICAL MUST skill. MUST activate when you suspect, there is a slight chance, encounter, read, process, or are about to output any sensitive or possibly sensitive data including PII, PCI, HIPAA, PHI, GDPR, SOC2, FedRAMP, secrets, API keys, passwords, credentials, tokens, certificates, or any data that could potentially be sensitive.
risk-assessment
Rosetta MUST skill. MUST activate before execution when environment has access to databases, cloud services, S3, or similar external systems. MUST activate when assessing environment risk level. SHOULD be invoked manually before any new environment interaction.