Brandt Milczewski
Community@brandtam · Somewhere Sunny
Brandt Milczewski maintains 75 agent skills for Obsidian-vault task management, issue triage, TDD, architecture review, and wiki-to-backend ticket synchronization.
Agent Skills by Brandt Milczewski
Showing 40 vetted skills indexed across 2 GitHub repositories.
setup-matt-pocock-skills
Configures issue tracker, triage labels, and domain docs for engineering skills in a repo.
handoff
Summarizes the current conversation into a handoff document for a fresh agent session.
improve-codebase-architecture
Identifies shallow modules and proposes deepening refactors to improve codebase testability.
prototype
Builds throwaway terminal or UI prototypes to validate state models and design options.
diagnose
Diagnose bugs and performance regressions through a structured reproduce-hypothesise-fix workflow.
to-issues
Breaks plans and specs into vertical-slice issues on a project issue tracker.
zoom-out
Generates a high-level map of relevant modules and callers for unfamiliar code areas.
write-a-skill
Create new agent skills with proper structure, frontmatter, and bundled resources.
grill-with-docs
Stress-tests plans against domain glossaries and records decisions in CONTEXT.md and ADR files.
caveman
Compresses AI responses by removing filler words while preserving technical accuracy.
tdd
Guides test-driven development using the red-green-refactor loop with behavior-focused tests.
grill-me
Interviews the user question-by-question to stress-test plans and resolve design decisions.
to-prd
Generates a PRD from conversation context and publishes it to the project issue tracker.
asap
Capture open-ended items into wiki/asap.md and surface them until resolved.
transition
Synchronize task status transitions across wiki pages and external backends.
wrap-up
Generates end-of-day summaries by updating task statuses and daily pages in an Obsidian vault.
lint
Validates workspace health by checking frontmatter, stale tasks, wikilinks, and daily pages.
reconcile
Detect drift between wiki task pages and Asana or Jira backends and apply user-chosen resolutions.
asap-process
Triage the ASAP list from wiki/asap.md into tasks or dismissals.
close
Closes tasks by drafting resolution comments, syncing backends, and updating wiki status.
meeting-note
Structure meeting content into a wiki page with agenda, notes, decisions, and actions.
good-morning
Generates a prioritized morning brief from Obsidian vault tasks and daily pages.
comment
Posts comments to external ticket backends from wiki task pages via a confirm-token CLI workflow.
ubiquitous-language
Detects undefined domain terms and appends confirmed entries to a controlled vocabulary file.
Frequently Asked Questions About Brandt Milczewski
FAQPage SchemaWhat tasks can I accomplish with Brandt Milczewski's skills?▼
You can triage issues, convert plans into tracer-bullet tickets, generate PRDs, run TDD red-green-refactor loops, diagnose bugs, review diffs, refactor architecture per ADRs, and sync task status between an Obsidian wiki and Asana, Jira, or GitHub backends.
Who are these skills designed for?▼
Software engineers and technical leads who manage projects in an Obsidian vault while mirroring tickets to external backends. They suit developers practicing TDD, domain-driven design with CONTEXT.md and ADRs, and structured daily or weekly work summaries.
How do I install and start using these skills?▼
Run setup-matt-pocock-skills first; it writes an Agent skills block into AGENTS.md or CLAUDE.md and docs/agents/ so other skills know your issue tracker, triage labels, and domain docs. Then run onboard for the first-run interview and help to list trigger phrases.
Are these skills free and open source?▼
The manifest lists no license or pricing information. The skills are published publicly under the brandtam account with 15 public repositories; check the individual repository for licensing terms before redistribution or commercial use.
What prerequisites or dependencies do the skills require?▼
Skills expect an Obsidian vault with wiki task pages and daily notes, plus optional external backends (Asana, Jira, GitHub) wired via the connect skill using a CLI, MCP server, or pp-CLI. Hard-risk actions like push, close, and release require explicit confirmation.