psi
Plan-spec-implement workflow for structured development. Only use when explicitly directed by user or when mentioned in project AGENTS.md file. Generates ephemeral plans in ~/.dot-agent/, applies specs to project docs, then implements test-first.
What this skill does
# PSI - Plan Spec Implement Structured workflow for planning, specifying, and implementing changes with documentation-first approach. ## When to Use **Only use when:** - Explicitly directed by the user - Mentioned in project `AGENTS.md` file **Do not use automatically** - this is an opt-in workflow, not a default. ## Core Workflow **Plan → Spec → Implement** Phases are **independent** - you can start with any phase, but all must ensure documentation stays up-to-date. ## Key Principles 1. **Ephemeral planning** - Plans stored in `~/.dot-agent/` (not committed) 2. **Documentation-first** - Specs applied to project docs/READMEs/AGENTS.md 3. **Test-first implementation** - Tests for docs/user journeys before code 4. **Design/review embedded** - Design and review integrated into Plan/Spec phases 5. **Phase independence** - Each phase can work standalone, all update docs ## Phase Overview ### Plan Phase - Generates detailed plans in `~/.dot-agent/repo/YYYY-MM-work-name.plan.md` - Research stored in `~/.dot-agent/working-dir/repo/YYYY-MM-work-name.research.md` - Embeds design considerations - Includes review before proceeding ### Spec Phase - Generates specs for: API schemas, interfaces, DTOs, database models, config, env vars, architecture, user journeys, package structure, tech choices - Embeds design considerations - Reviews specs before applying - Applies to: `docs/`, README.md files, AGENTS.md files ### Implement Phase - Test-first: tests for docs/user journeys before code - CI verification: verify types, tests, lint pass before committing - Atomic commits: group related changes with tests - Updates docs, README.md, AGENTS.md as code evolves - Can work independently if specs exist in docs ## Research Management Detects phrases like: - "looking at your research" → Loads research file - "refine your research" → Updates research file, narrows focus ## Documentation Structure - **README.md**: Aim for < 1000 lines (not hard rule), can be longer if needed - **AGENTS.md**: < 200 lines, inline at root/packages/modules/code level - **docs/**: Architecture, roadmap, tech-choices, setup/, user-journeys/, design/ ## References For detailed protocols, see: - `references/plan-phase.md` - Plan generation with embedded design/review - `references/spec-phase.md` - Spec generation and application - `references/implement-phase.md` - Test-first implementation - `references/review-protocol.md` - Reviewing plans/specs/design - `references/research-management.md` - Research file handling - `references/docs-structure.md` - Documentation organization rules - `references/file-paths.md` - Storage paths and conventions
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.