It is clear in your head, but hard to explain completely.
Important details appear only after building starts, so the project keeps changing and the same questions come back.
SKILL GARDENInsight, before thought.
CODE SOUL / SKILL GARDEN
From a human ideato a working agent.
Two skills. One rigorous path.
01Discover→02Specify→03Build→04Prove
Requirements upstream. Product delivery downstream.A SMALL MYCELIUM BREAK
Pick a pixel mushroom.
It moves through the network. Catch it before it grows somewhere else.
Picked00
MYCELIUM / FORAGEClick or press Enter
05 species in rotation
FOR VIBE CODERS WHO KNOW THEIR BUSINESS
Put your attention back where it belongs: the product.
You know the users, the business and what the product should achieve. The difficulty is preserving that clarity through system decisions, implementation and launch.
WHERE GOOD IDEAS BREAK
A good idea usually breaks in one of three places.
The problems begin when your business judgement must become complete requirements, sound system decisions and a reliable release.
The business is clear, but the system is not.
Who can use what, where information comes from, and what happens when things go wrong are decided too late.
The Vibe Coding demo works. Launch is another story.
More users, failures, restarts and everyday maintenance expose problems the first demo never had to handle.
OUR ANSWER
We built two Skills to solve the problems above.
One makes the product precise enough to build. The other turns that approved plan into a tested, documented Agent product—so you can stay focused on the business and the experience.
01 / UPSTREAM READY
Agent Native Requirements
Use it when you know the goal but cannot tell whether the request is complete. It talks through real situations in everyday language, closes the missing decisions, and records the right foundation for every part of the product.
WHEN IT HELPS- You want a customer follow-up tool, but are unsure what salespeople should provide and receive.
- You are moving an offline workflow online, while permissions and unusual cases keep causing rework.
- Your Vibe Coding demo is useful, but nobody can agree on what “ready to launch” actually means.
02 / DOWNSTREAM READY
Agent System Builder
Use it when the business rules are clear but designing a complete Agent still feels like a specialist’s job. Hypha is the recommended base, not a requirement: each part can follow official releases, use deeply customized source, combine both, or take another suitable route.
WHAT IT CAN BECOME- A service Agent that reads policy, checks an order and knows when to ask a person.
- A research or content Agent that receives materials, checks sources and delivers the right format.
- An operations Agent that runs repeatable tasks, records the result and asks before risky actions.
A HANDOFF, NOT A HANDWAVE
Every decision survives the journey.
Talk like a user
The requirements skill asks concrete questions about real scenarios, inputs, outputs, data, risk and quality.
Freeze the contract
Unknowns, assumptions and acceptance cases are resolved before implementation begins.
Choose each part’s foundation
Use official releases when available, pinned source for deep customization, or another approved route when it fits better.
Prove the product
Failures are repaired and retested until the documented user journey works from a clean start.
THE STAR GATE
Support the roots. Unlock the skills.
Sign in with GitHub and star both open-source foundations. We verify the two stars directly with GitHub before enabling private, always-current Skill archives.
Read-only identity and star status. The server downloads private archives for you; your GitHub account never receives private-repository access.
codesoul://skill-access- ·STEP 01Sign inGHContinue with GitHub
- ·STEP 02Star PlasmodWaiting☆ Star on GitHub ↗
- ·STEP 03Star HyphaWaiting☆ Star on GitHub ↗
Complete the steps above to unlock both archives.
Source-available · noncommercial licenseUSE IT ON A REAL PROJECT
Give your coding agent one direct instruction.
After downloading and extracting a Skill, paste one of these prompts into the agent working on your real project. Replace the bracketed text with your project.
Help me install the agent-native-requirements Skill from the ZIP I downloaded, then use it to define my real project: "[project name / problem]". Ask me direct, scenario-based questions until the requirements are complete enough for an engineering agent to build without coming back to me.
Help me install the hypha-domain-builder Skill from the ZIP I downloaded. Read the approved requirements and module adoption plan for "[project name]", then build, test, fix, and document the complete Agent product. Use pinned Hypha packages, source, or a hybrid only where the plan selects them and availability is verified; otherwise follow the approved other-framework or project-owned route.
RECOMMENDED OPEN-SOURCE ROOTS
Strong foundations when the product needs them.
Plasmod offers a native evidence and memory substrate. Hypha offers a governed, replayable runtime. They are CodeSoul’s recommended foundations, while each project still chooses what fits module by module.
Models & datasets on Hugging Face↗
AGENT-NATIVE DATABASE · GO
Plasmod
Models event, memory, state, artifact and relation as first-class cognitive objects. Retrieval returns provenance, proof traces and graph context—not only similar fragments.
Event-drivenStructured evidenceWorkspace isolation
Visit Plasmod website ↗AGENT SYSTEM FRAMEWORK · TYPESCRIPT
Hypha
A harness-oriented framework for agent systems that can be run, governed, traced, replayed, evaluated and extended through stable Domain and runtime contracts.
ReAct + FSMGoverned toolsReplay & evaluation
Visit Hypha website ↗MUSHROOM COMMUNITY
Build with people who care about the roots.
Join the CodeSoul discussion community for release notes, implementation patterns, early experiments and conversations around agent-native systems.
Scan with WeChat to joinThe QR code opens the Mushroom knowledge community.
COMMUNITY / 2026