From mycelium
Auto-detects tech stack in new/unfamiliar codebases, verifies build/test/lint tooling, documents code patterns, and scaffolds Architecture Decision Records.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mycelium:delivery-bootstrapThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Just-in-Time tech stack detection and setup.
Just-in-Time tech stack detection and setup.
.claude/diamonds/active.yml:
product_type is set (from /mycelium:interview), use it to determine the delivery profile.${CLAUDE_PLUGIN_ROOT}/jit-tooling/detector.md Step 1b:
content_coursecontent_publicationcontent_mediaai_toolservice_offering1b. Scan project root for technology indicators (software and ai_tool with code):
Identify stack components (software/ai_tool with code):
Verify tooling works:
Document existing patterns:
Scaffold Architecture Decision Records (if applicable):
docs/adr/ directory and a template file docs/adr/0000-template.md:
# [NUMBER]. [TITLE]
Date: [DATE]
## Status
Proposed | Accepted | Deprecated | Superseded by [ADR-XXXX]
## Context
What is the issue that we're seeing that is motivating this decision?
## Decision
What is the change that we're proposing and/or doing?
## Consequences
What becomes easier or more difficult to do because of this change?
Output:
## Stack Profile
- Language: [x] v[y]
- Framework: [x]
- Package manager: [x]
- Test: [command] ([framework])
- Lint: [command]
- Build: [command]
- CI/CD: [platform]
## Commands
- Install: [command]
- Dev server: [command]
- Test: [command]
- Build: [command]
- Lint: [command]
## Observed Patterns
- [list of patterns detected]
## Issues Found
- [any broken tooling or warnings]
## Architecture Decision Records
- Scaffolded: yes/no
- Location: docs/adr/
- Pending decisions: [list if any identified during bootstrap]
Create/update ${CLAUDE_PLUGIN_ROOT}/jit-tooling/active-stack.yml with detected stack configuration.
See ${CLAUDE_PLUGIN_ROOT}/jit-tooling/active-stack.example.yml for the expected format.
npx claudepluginhub haabe/mycelium --plugin myceliumAnalyzes existing codebases to detect project types, frameworks, structures, and collision risks. Supports context, brownfield, and setup modes for feature planning.
Scans codebase to auto-generate CLAUDE.md project config and .rune/ state files for full context in AI coding sessions. Use on new repos or missing/stale context.
Scans codebase, infers project configuration, and interactively generates SDLC files with confidence-driven questions.