minimum-viable-agentic
Guide creation of minimum viable agentic layer for a codebase. Use when starting agentic coding in a new project, bootstrapping essential components, or creating the minimal scaffolding for agent success.
What this skill does
# Minimum Viable Agentic Layer Skill
Guide teams through creating the essential agentic layer components to start agentic coding.
## When to Use
- Starting agentic coding in a new project
- Adding agentic layer to existing codebase
- Understanding bare minimum requirements
- Quick-starting agentic automation
## Core Concept
> "For your minimum viable agentic layer, you really only need these pieces: AI developer workflow directory, prompts, and plans."
## Minimum Viable Structure
```text
project/
├── specs/ # Plans for agents
│ └── (generated plans go here)
├── .claude/
│ └── commands/ # Agentic prompts
│ ├── chore.md # Chore planning
│ └── implement.md # Implementation HOP
└── adws/ # AI Developer Workflows
├── adw_modules/
│ └── agent.py # Core execution
└── adw_chore_implement.py # Gateway script
```
Total: 4-5 files to bootstrap.
## Implementation Workflow
### Step 1: Create Directory Structure
```bash
mkdir -p specs
mkdir -p .claude/commands
mkdir -p adws/adw_modules
```
### Step 2: Create Chore Template
`.claude/commands/chore.md`:
```markdown
# Chore Planning
Create a detailed plan for this chore task.
## Task
$ARGUMENTS
## Output
Create a spec file at: specs/chore-{adw_id}-{name}.md
Include:
- Task description
- Files to modify
- Step-by-step implementation
- Validation criteria
```
### Step 3: Create Implement HOP
`.claude/commands/implement.md`:
```markdown
# Implementation
Implement the plan provided.
## Plan File
$ARGUMENTS
Read the plan file and implement each step.
Report changes with git diff --stat when complete.
```
### Step 4: Create Agent Module
`adws/adw_modules/agent.py`:
- Claude Code subprocess execution
- Request/response data models
- Output file handling
- Error handling
### Step 5: Create Gateway Script
`adws/adw_chore_implement.py`:
- Accept chore description
- Execute /chore to generate plan
- Execute /implement with plan
- Report results
## Validation Checklist
After setup, verify:
- [ ] `specs/` directory exists
- [ ] `.claude/commands/chore.md` exists
- [ ] `.claude/commands/implement.md` exists
- [ ] `adws/adw_modules/agent.py` exists
- [ ] Gateway script runs successfully
## Time Investment
| Phase | Time | Activities |
| --- | --- | --- |
| Setup | 2 hours | Directory structure, basic templates |
| Agent module | 2-4 hours | Core execution code |
| Gateway script | 1-2 hours | First composed workflow |
| **Total** | **5-8 hours** | **MVP complete** |
## Scaling Path
After MVP, add progressively:
1. **Week 2**: Add /bug and /feature templates
2. **Week 3**: Add hooks for automation
3. **Week 4**: Add triggers for scheduling
4. **Week 5**: Add worktree isolation
5. **Week 6+**: Add full SDLC workflows
## Key Memory References
- @agentic-layer-structure.md - Full structure reference
- @gateway-script-patterns.md - Script patterns
- @template-engineering.md - Template design
## Output Format
```markdown
## Minimum Viable Agentic Layer Setup
**Project:** {name}
**Status:** Ready for Implementation
### Files to Create
1. **specs/** (directory)
- Will contain generated plans
2. **.claude/commands/chore.md**
- Chore planning template
- Generates specs from descriptions
3. **.claude/commands/implement.md**
- Implementation HOP
- Executes generated plans
4. **adws/adw_modules/agent.py**
- Core agent execution
- Subprocess handling
- Output management
5. **adws/adw_chore_implement.py**
- Gateway script
- Composes chore + implement
### Implementation Order
1. Create directories
2. Add chore.md template
3. Add implement.md template
4. Create agent.py module
5. Create gateway script
6. Test end-to-end
### Estimated Time
5-8 hours to production-ready MVP
```
## Common Mistakes
- Over-engineering MVP (too many templates too soon)
- Skipping agent.py (trying to call claude directly)
- No error handling in gateway scripts
- Not organizing output files consistently
## Version History
- **v1.0.0** (2025-12-26): Initial release
---
## Last Updated
**Date:** 2025-12-26
**Model:** claude-opus-4-5-20251101
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.