with one click
bash_profile
bash_profile contains 4 collected skills from MichaelRBond, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Create spec and implementation plan documents optimized for both human reviewers and AI coding agents. Use this skill whenever someone asks to write a spec, PRD, implementation plan, technical design document, project plan, or any planning document that will guide development work — especially work done by Claude Code or other AI coding agents. Also use when someone wants to restructure, reorganize, or improve an existing spec or planning document. Trigger on phrases like 'write a spec', 'create a plan', 'implementation document', 'break this into tasks', 'project planning', 'technical design', or when someone mentions their spec is too long, hard to review, or not working well with AI agents.
Review a GitHub PR using ACR (Agentic Code Reviewer), filter false positives, and produce a ready-to-post review. Reads PR context from $DEVDASH_CONTEXT when launched from devdash, or can be invoked manually.
Use when the user invokes /acr-review or asks to run the ACR review loop, external code review cycle, or iterative review process. Orchestrates an automated code review feedback loop using ACR (Agentic Code Reviewer). Never runs automatically.
Store planning documents, specs, architecture docs, meeting notes, task breakdowns, and other markdown artifacts in Obsidian via the Obsidian CLI -- so they sync across devices automatically. Use this skill whenever you would create a planning document, design doc, spec, specification, design spec, test spec, refactor spec, roadmap, ADR, sprint plan, meeting note, or any project-related markdown artifact. Also use when the user says "plan", "write a spec", "spec this out", "specification", "document this", "write up", "note this", "track this", "decision record", "save to obsidian", "sync to obsidian", or asks you to create any markdown file that is not source code. This includes ANY file that would otherwise go in a docs/, specs/, or design/ folder in the repo -- those files belong in Obsidian, not in the repo. Do NOT use this skill for README.md or other files that belong in the repo itself.