- the whole hatch3r governance needs a full rewrite for 2.0.0. We did some brainstorming about what it should look like. Make sure to not miss any possibly important question within the interview that matters when building such a framework at worldclass, leading and industry standard level. Here is the list: 



--End user + Governance + Audit cycles--

industry standard and state of the art hatch3r cli + hatch3r cli lifecycle

Full Adapter support & capability utilization + Workspace + Worktree support

State of the art and industry standard External platform integration (GH, ADO, GL) +  Board lifecycle coverage

CLI-tool-Native instead of MCP 

World class, industry standard and scientifically + real world proven best possible Customizability, own content creation

World class, industry standard and scientifically + real world proven best possible spec creation for greenfield + brownfield projects

World class, industry standard and scientifically + real world proven best possible core hatch3r-workflow

World class, industry standard and scientifically + real world proven best possible of each hatch3r agent, skill, rule and command

Most consitent and reliable dynamic agent / skill / rule routing within each hatch3r agentic iteration for the end user so it always uses the ideal prompts for any task

Always ideal set of each content group (rules, skills, agents, commands) to cover the full zero-to-one software product development lifecycle winning in the real world, ideally each with own dedicated  skills / agents / rules

Strong, dedicated focus of hatch3r agents on UI, UX, Security, mainainability, reliability & testability, scalability, performance and enhancability and generally all priciples of building software at any stage as fast as possible with the highest possible quality, ideally dedicated contents for each of the mentioned pillars (including the perhaps missing ones)

No over-engineering for end users; early stage software / solo team doesnt need enterprise / overly mature monitoring for example;

Strong Focus on Human traits with outside in view within governance and each hatch3r content for real world exceling

Ideal Dynamic hatch3r workflow effort & token usage for every task to achieve any task with best possible quality the fastest possible with as little tokens as possible. 

Strong focus on triage & understanding of every agentic task via native question tool + dynamic amounts of sub agents at all workflow steps to achive the best possible end results for the end user, NO MATTER how many sub agents and mandatory general sub agentic orchestration and also display of how many sub agents the main agent is gonna use within the plan

Strong focus on web research during all hatch3r workflows when relevant to always have proven outside context when achieving a task

native browser automation with playwright CLI as key component in every agentic task (still as opt in)

Strong focus on agentic & prompt security

Ideal standartized iteration summary after each hatch3r powered run

focus on Pattern recognition, reuse of whats available in the code, cetralization and reuse where possible -> always provide code minimum as good as the existing, ideally better and as good as possible

Maintainablity, enhancability, anti duplicatation etc., is one of the highest prios when hatch3r agents write code

Strong focus on Anti slop, write code as the most senior humans would

most reliable Hallucination / assuption control / prevention possible in every agentic iteration for every agent ever using hatch3r prompts -> always work with proof

when writing tests, always try to test the real deal with as little mocking possible. Written hatch3r tests must be of highest value possible without overhead and overengineering providing state of the art and industry standard testing. 

--Governance + Audit cycles only--

Research related agentic software engineering trends in the web that could enhance hatch3r to the good during audit cycle to always stay at the front and top

World class and industry standard comprehensive and user friendly end user documentation in-repo and on the public website

World class OSS repo + npm maintenance

High level, comprehensive but also technical release notes & changelog

governance + audit cycle self auditing with the same scientific and real world proof approach

- capability analysis for adapter features needs to be intensified. Currently seems missing out on a lot hatch3r could support / build on. 
- Needs to be more holistic, innovative and disruptive in every aspect and audit domain. For example it should research what the perfect implementer agent looks like and compare it to the current, being open for big changes / refactors. 
- Every audit results in too many findings, some false positives, some irrelevant or not improving the framework or moving it further towards the goal. Only findings with real near or long term affect should be registered. 
- Audit execute consumes more agentic resources as necessary; should for high, medium and low group findings and allocate one agent to it, not one for each finding. 1 per critical is fine though. 
- audit cycle should when auditing contents look out for existing similar contents in the web with good reputation to compare and inspire so the hatch3r contents are the perfect mix between science and working in real world already. 
- The set / constellation / architecture of hatch3r contents themselves also needs auditing to identify missing ones, obscolete ones or mergable / fusionable ones.
- generally there must be a golden mix of science and real world proof when it comes to hatch3r capabilities 


I may have missed many points. There might be duplications. Feel free to ask as many additional questions for any possibly important topic / priciple. Use the question tool. 
