Adhd Orchestration Skill
D 58 completed
Other
unknown / markdown · tiny
7
Files
1,667
LOC
0
Frameworks
1
Languages
Pipeline State
completedRun ID
#1546280Phase
doneProgress
0%Started
2026-04-16 23:55:43Finished
2026-04-16 23:55:43LLM tokens
0Pipeline Metadata
Stage
CatalogedDecision
proceedNovelty
14.96Framework unique
—Isolation
—Last stage change
2026-05-10 03:35:17Deduplication group #47247
Member of a group with 11,584 similar repo(s) — canonical #1453550 view group →
Powered by Repobility — scan your code at https://repobility.com
AI Prompt
Create a multi-terminal orchestration system designed to help developers with ADHD manage complex coding projects. I need a system that diagnoses the domain health, traces dependencies across multiple layers, and distributes work across several parallel sessions. The core functionality should involve a mothership orchestrator that manages the flow through phases like reconstruction and dependency deep-dives. Please structure this using a 5-layer stack concept, incorporating skills for decomposition, debate, and state persistence.
markdown orchestration ai-coding development-workflow system-design cli adhd llm-tooling
Generated by gemma4:latest
Catalog Information
Create a multi-terminal orchestration system designed to help developers with ADHD manage complex coding projects. I need a system that diagnoses the domain health, traces dependencies across multiple layers, and distributes work across several parallel sessions. The core functionality should involve a mothership orchestrator that manages the flow through phases like reconstruction and dependency deep-dives. Please structure this using a 5-layer stack concept, incorporating skills for decomposit
Tags
markdown orchestration ai-coding development-workflow system-design cli adhd llm-tooling
Quality Score
D
57.6/100
Structure
32
Code Quality
100
Documentation
30
Testing
0
Practices
78
Security
100
Dependencies
50
Strengths
- Low average code complexity — well-structured code
- Good security practices — no major issues detected
Weaknesses
- No LICENSE file — legal ambiguity for contributors
- No tests found — high risk of regressions
- No CI/CD configuration — manual testing and deployment
Recommendations
- Add a test suite — start with critical path integration tests
- Set up CI/CD (GitHub Actions recommended) to automate testing and deployment
- Add a linter configuration to enforce code style consistency
- Add a LICENSE file (MIT recommended for open source)
Languages
Frameworks
None detected
Embed Badge
Add to your README:
