Menu
Test-driven development workflow. Use when the user says /tdd or wants to build a feature test-first. Guides red-green-refactor cycle.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Run end-to-end smoke tests for the Mycelium stack. Verifies install, memory, search, coordination, and OpenClaw integration. Use when validating a release, after a deploy, or when something feels broken.
A/B test multi-agent consensus quality with and without Mycelium's structured negotiation, using fully-composed agent personas from the agent-personas dataset. Pick a named scenario (e.g. ex07_investment_portfolio) and the skill fetches the right personas, builds SOUL.md for each agent, then runs the standard before/after flow.
Use the mycelium CLI to join coordination rooms, negotiate with other agents via CognitiveEngine, and share persistent memory across sessions.
Multi-agent coordination layer with persistent memory. Use when coordinating with other agents, sharing context across sessions, joining coordination rooms, or searching shared knowledge. Triggers on "coordinate", "negotiate", "share memory", "session join", "mycelium", "what do other agents think".
Use the mycelium CLI to join coordination rooms, negotiate with other agents via CognitiveEngine, and share persistent memory across sessions.
Run end-to-end smoke tests for the Mycelium claude_code adapter. Verifies claude CLI prereqs, daemon installation, single-host cold-spawn dispatch, multi-room ownership semantics, notes persistence across spawns, control verbs (status/abort), budget gating, concurrent dispatch serialization, and (with funded API credits) autonomous coordination via mycelium-daemon coordination_tick handling. Use when validating the claude_code adapter after changes to `integrations/claude_code/**`, the daemon, or after upgrading the `claude` CLI itself.
| name | tdd |
| description | Test-driven development workflow. Use when the user says /tdd or wants to build a feature test-first. Guides red-green-refactor cycle. |
Guide the user through a red-green-refactor TDD cycle.
Clarify — Ask the user what feature or fix they want to build. Understand the expected behavior.
Write failing test — Write a test that describes the desired behavior. The test should be specific and minimal.
Run test (red) — Run the test to confirm it fails:
cd fastapi-backend && python -m pytest tests/<test_file>.py -x -q
Show the failure output. This is the "red" phase.
Implement — Write the minimum code to make the test pass. No more, no less.
Run test (green) — Run the test again to confirm it passes. This is the "green" phase.
Refactor — If the implementation can be improved, refactor while keeping the test green.
Full suite — Run the full test suite to ensure nothing else broke:
cd fastapi-backend && python -m pytest tests/ -x -q
Repeat — Ask if the user wants to add another test case or move on.