aio-ideate
Skill0 starsChanged 31 days agoMITView on GitHub
Generate and rank backend or agent-system approaches before committing to a design.
In this repository54 other files it gives its agents.
- agent-workflowsSkill
- aio-agentsSkill
- aio-algorithmsSkill
- aio-apiSkill
- aio-architectureSkill
- aio-autoplanSkill
- aio-benchmarkSkill
- aio-brainstormSkill
- aio-canarySkill
- aio-checkpointSkill
- aio-ciSkill
- aio-commitSkill
- aio-compoundSkill
- aio-dataSkill
- aio-debugSkill
- aio-devex-reviewSkill
- aio-doc-reviewSkill
- aio-explainSkill
- aio-feedbackSkill
- aio-handoffSkill
- aio-observeSkill
- aio-optimizeSkill
- aio-pipelinesSkill
- aio-plan-reviewSkill
- aio-planSkill
- aio-proofSkill
- aio-prototypeSkill
- aio-qa-onlySkill
- aio-qaSkill
- aio-releaseSkill
- aio-resumeSkill
- aio-reviewSkill
- aio-securitySkill
- aio-shipSkill
- aio-simplifySkill
- aio-specSkill
- aio-tddSkill
- aio-test-auditSkill
- aio-testSkill
- aio-verifySkill
- aio-workSkill
- aio-worktreeSkill
- all-in-oneSkill
- apple-appstore-reviewerSkill
- backend-algorithmsSkill
- backend-debugSkill
- backend-pipelinesSkill
- backend-planSkill
- backend-reviewSkill
- backend-verifySkill
- complete-destructionSkill
- launch-readinessSkill
- play-policy-insightsSkill
- reverse-engineer-anythingSkill
The file
Files
AIO Ideate
Generate and rank backend or agent-system approaches before committing to a design.
Protocol
- Establish the operational problem, caller/job, observable failure or opportunity, constraints and accepted scope. Read existing architecture and incidents before proposing new infrastructure.
- Generate a small set of materially different mechanisms: improve the current service, queue a bounded job, use an explicit agent state machine, or introduce durable orchestration only when its recovery benefit is needed.
- Rank candidates using correctness, recovery, tenant/trust boundaries, latency/cost, migration risk and the strength of available evidence. Separate known facts from assumptions; state which measurement could reverse the ranking.
- Recommend a candidate and retain rejected alternatives with reasons. Route uncertain product outcomes to aio-brainstorm, and a settled outcome to aio-spec.
Return and handoff
A ranked backend decision brief with evidence, alternatives, uncertainties and the recommended next stage. Ideas do not authorize implementation.
In a pipeline, use the stage contract and return to the integrating controller. Run only this specialist's owned scope; preserve the user's accepted decisions and existing authorization.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.