PromptWorks

Private version-controlled mirror of AI skills used in my daily workflow.

Generated by sync-skills.ps1; do not edit manually.

Skills

Skill	Description
ado-triage	Triage Daniel's Azure DevOps work items assigned to him across both orgs - OE on office.visualstudio.com and ES365 on dev.azure.com/enginfra. Categorizes each open item as needing an update, missing KB info, or stale/needs cleanup; scores severity and importance using Obsidian KB context; then walks through updates one at a time. Triggers: /ado-triage, check my ADO queue, triage my work items, review my work item queue, go through my ADO items, what am I assigned, my ADO backlog.
brainstorming	Explore intent, requirements, and design BEFORE any creative or build work - new features, components, functionality, behavior changes, refactors, or new tools and scripts. Produces a reviewed spec instead of jumping straight to code. Use when a request is vague, open-ended, or bigger than a one-line change, and any time the user says: let us build X, can you add X, I want a tool that, how should we design this, brainstorm, spec this out, what are the options. Run before writing-plans.
chapan	Mission control for the Chapan Hokkaido relocation project. Dashboard, router, and digest over the tracker at D:\Repos\Chapan. Use when the user says /chapan, "chapan", "chapan status", "chapan dashboard", "chapan digest", or asks how the Japan/Hokkaido relocation is going. Routes to chapan-intake, chapan-visa, chapan-programs, chapan-leads.
chapan-intake	The recurring interview for the Chapan Hokkaido relocation mission. Use when the user says "chapan check-in", "chapan intake", "chapan interview", /chapan-intake, or when a weekly nudge asks Daniel for a relocation status update. Interviews Daniel, updates D:\Repos\Chapan profile.md and status.md, appends a dated log, and turns his findings into tracked visa/program/lead dossiers.
chapan-leads	Deep-dive a specific Hokkaido locality (or a program at a locality) into a structured dossier for the Chapan relocation mission by investigating its official municipal/prefectural website. Use when the user says "chapan lead", "chapan leads", "investigate ", /chapan-leads, or names a Hokkaido town/village to research. Writes D:\Repos\Chapan\leads\Hokkaido\.md and keeps the leads index current.
chapan-programs	Research and track Japanese relocation and rural-revitalization support programs for the Chapan Hokkaido mission — national (移住支援金, 起業支援金, 地域おこし協力隊, 空き家バンク) and Hokkaido prefectural/municipal. Use when the user says "chapan programs", /chapan-programs, or asks about relocation grants, subsidies, akiya banks, or revitalization schemes. Writes/updates D:\Repos\Chapan\programs\*.md with source URLs and retrieved dates.
chapan-visa	Research and track Japanese visa pathways for the Chapan Hokkaido relocation, evaluated against Daniel's family profile. Use when the user says "chapan visa", /chapan-visa, asks which visa fits, or wants visa requirements/rules checked or refreshed. Searches official sources (ISA, MOFA, JETRO), writes/updates D:\Repos\Chapan\visa\*.md dossiers with a source URL and retrieved date.
clawpilot-chats-digest	Generate an on-demand digest of recent activity in the Clawpilot/Lobster Pound Teams spaces — the new MCAPS Lobster Pound channel (primary, going forward) plus the two original group chats (MCAPS Lobster Pound and 'ClawPilot: From Copilot to Agent') — surfacing major Clawpilot releases, novel usage patterns, and items worth a closer look for Daniel. Triggers: /clawpilot-chats-digest, 'clawpilot digest', 'clawpilot chats digest', 'what's new in the clawpilot chats', 'lobster pound digest'.
clawvibe	Explicitly invoked (e.g. /clawvibe, "let's clawvibe this", "run the full workflow on this") to route a specific task through the complete brainstorm -> plan -> implement -> review -> finish pipeline using the locally installed skills. Does NOT trigger automatically — opt-in only, unlike a standing gatekeeper.
connect	Manage Microsoft Connect (perf review) tracking inside the Obsidian vault. Reads the active Connect markdown in D:\Repos\Obsidian\04 - Connects\, cross-references the rest of the vault for evidence (daily notes, squad meetings, status updates, decisions), and emits weekly check-ins, draft narratives, 1:1 prep digests, and gap warnings. Triggers: 'connect', 'connect check-in', 'connect prep', 'connect draft', or any /connect subcommand.
dispatching-parallel-agents	Fan work out to multiple sub-agents at once when a task splits into 2+ independent pieces with no shared state or ordering dependency - auditing several modules, researching unrelated questions, or applying the same change across separate files. Covers agent prompt structure, common mistakes, and verifying results after agents return. Triggers: do these in parallel, spin up agents, run these at once, split this work, parallelize this.
executing-plans	Execute an already-written implementation plan document task by task, with verification and review checkpoints between steps. Use when a plan.md or spec already exists and the work now needs carrying out, including knowing when to stop and ask for help versus revisit earlier steps. Triggers: execute the plan, work through the plan, implement the plan, start on the plan, next task in the plan, follow the spec. Pairs with writing-plans and subagent-driven-development.
finishing-a-development-branch	Decide how to integrate finished work once implementation is done and tests pass - verifies tests, detects the environment, determines the base branch, then presents structured options (merge, open a PR, keep the branch, or discard) and cleans up the workspace or worktree afterward. Triggers: I am done with this branch, wrap this up, merge this, should I open a PR, finish the feature, clean up the worktree, what do I do with this branch now.
flow-1on1	Prep Daniel's biweekly 1:1 with his manager Ahmed Atya (ES365 FLOW team). Reviews activity since the last 1:1, co-authors Ahmed's four-question notebook-tracker template one section at a time, writes the dated entry into the Daniel-Ahmed.docx tracker, then builds a private talking-points and issues brief. Triggers: /flow-1on1, prep my Ahmed 1:1, 1:1 with Ahmed, notebook tracker, manager 1:1 prep, flow 1:1.
get-meeting-transcript	Grab a Teams/Stream meeting transcript by driving a logged-in browser when the Graph download is blocked. Captures the underlying .vtt from network traffic, or scrapes the recap transcript pane. Accepts a Teams recap, Stream/SharePoint, or meet.microsoft.com URL, or a calendar reference it resolves to one. Saves .vtt + .md + the meeting chat into the Obsidian vault. Triggers: get transcript, scrape transcript, grab the transcript, meeting chat, transcript for my meeting.
kb	Vault-first recall. Search Daniel's Obsidian KB (D:\Repos\Obsidian) BEFORE WorkIQ/M365, Azure DevOps, IcM, or the browser. Use for any lookup: "who is X", "what's my/his alias, SC-ALT, email, ID, manager, office", "what did we decide about X", "when did we meet about X", "what is ", "remind me", "do we know", "look it up", "check the KB", plus anything about squads, Connects, RISE, meetings, daily notes, or people Daniel works with.
kblinter	Run the knowledge-base linter against the Obsidian vault at D:\Repos\Obsidian and surface the findings. Use whenever the user asks to lint, audit, or check the health of the vault/Second Brain. Triggers: /kblinter, "lint the vault", "audit my notes", "check vault health", "run the kb linter", "find orphan notes", "find broken links in the vault".
lights-out	Use when the user is going to bed, going away, or wants unattended overnight coding work; says "lights out", "run this overnight", "keep working while I sleep", or names gnhf; asks to check on, steer, or stop a running overnight job; asks "how did last night's run go", says "good morning", or wants a morning review of an agent run; or gives review findings on the results of an overnight run.
mslearn	Query the live Microsoft Learn MCP for grounded, first-party docs, code samples, and full-page fetches across Azure, M365, .NET, and Power Platform. Use when the user asks what Microsoft says about X, needs an authoritative answer for a customer, wants current official guidance, looks for a code sample, or asks to cite or quote the docs. Triggers: ms learn, microsoft learn, learn docs, look it up on learn, cite the docs, official microsoft guidance, what do the docs say.
oneonone-pokedex	IC-side companion for Daniel's recurring 1:1 with his manager - the mirror of the manager coaching-pokedex. Preps an agenda from the Obsidian vault, reflects on a recorded 1:1 with an honest self-scorecard of how Daniel showed up (never grading the manager), assigns a Pokemon for session energy, tracks trends, and writes notes back to the vault as Connect evidence. Private. Triggers: /1on1, /oneonone, 1:1, one on one, prep for my 1:1, reflect on my 1:1, manager sync.
receiving-code-review	Handle incoming code review feedback with technical rigor instead of reflexive agreement - verify each claim, push back with evidence when a suggestion is wrong or does not apply, ask when feedback is unclear, and apply a YAGNI check before adding suggested professional features. Covers GitHub thread replies and implementation order. Triggers: here is the review feedback, address these comments, the reviewer said, respond to this PR comment, they want me to change.
requesting-code-review	Request an independent review of completed work before merging or declaring it done - builds the reviewer prompt, states what was implemented, the requirements, and the exact git range to review, and demands a read-only critical review with calibrated severity. Triggers: review my changes, can you check this over, is this ready to merge, get a second opinion, code review this, check my work before I ship it.
rise-15-5	Co-author and post Daniel's weekly RISE 15-5 status update to the "RISE Standups" Loop doc. Reviews the past week's activity, walks through each required section (Accomplishments, Work in Progress, Blockers/Risks, Focus for Next Week, Help Needed) one at a time for feedback/co-authoring, then posts the finished entry to the shared Loop doc. Triggers: /rise-15-5, "my 15-5", "weekly status", "post my 15-5", "RISE status update".
scratchpad-cleanup	Use when tidying, auditing, or freeing space in the Scratchpad working folder at D:\Repos\Scratchpad - the weekly sweep or an ad-hoc pass. Also use when reviewing or restoring files quarantined under _trash, or deciding whether a scratch artifact should be promoted into the Obsidian vault. Triggers: /scratchpad-cleanup, clean up scratchpad, tidy scratchpad, scratchpad is a mess, what can I delete in scratchpad, restore from _trash.
subagent-driven-development	Execute a multi-task implementation plan in the current session by dispatching each task to an implementer sub-agent and then a reviewer sub-agent, with pre-flight plan review, model selection, status handling, and durable progress tracking between tasks. Use when the plan has independent tasks and you want them built and reviewed without burning main-session context. Triggers: work through the plan with subagents, delegate these tasks, build this out task by task.
systematic-debugging	Find the actual root cause before proposing any fix - investigate, analyze patterns across similar cases, form and test a hypothesis, then implement. Use at the first sign of ANY bug, test failure, crash, error message, flaky test, or behavior that does not match expectations, and especially when tempted to try a quick patch. Triggers: this is broken, it is failing, why does this not work, weird error, test is red, it worked yesterday, intermittent failure.
teams-export	Export Microsoft Teams messages (1:1 chats, group chats, and channel posts) into the Obsidian vault at D:\Repos\Obsidian\00 - Chats\ as markdown. Reads the user-maintained source list at D:\Repos\Obsidian\00 - Chats\sources.yaml to know what to copy. The invoking prompt or automation decides the time range (e.g. last N messages, today, since last export, explicit date range). Triggers: 'teams export', 'export chat', 'export channel', 'copy teams messages', '/teams-export'.
test-driven-development	Write the failing test before the implementation, for every feature or bugfix - red, green, refactor. Use before writing any implementation code, and when fixing a bug (reproduce it as a failing test first). Covers what makes a good test, why the order matters, the rationalizations that mean you are skipping it, and a verification checklist before marking work complete. Triggers: add a feature, fix this bug, implement X, write tests, TDD.
using-git-worktrees	Ensure feature work happens in an isolated workspace before it starts - detects existing isolation, creates a git worktree or native isolated workspace, sets up the project, and verifies a clean baseline. Use before executing an implementation plan or starting anything that should not disturb the current working tree. Triggers: start a new feature, work on this separately, set up a branch for this, isolate this work, spin up a worktree.
verification-before-completion	Gate any completion claim behind actual evidence - run the build, tests, or linter and read the output before saying something is done, fixed, passing, or ready. Use right before committing, opening a PR, marking a task complete, or telling the user it works. Covers the common failure modes and the red flags that mean you are about to claim success you have not verified. Triggers: is it done, are we finished, ship it, mark it complete.
writing-plans	Turn a spec or set of requirements into a written, bite-sized implementation plan BEFORE touching code - scope check, file structure, right-sized tasks with no placeholders, global constraints, and a self-review pass, ending in a handoff for execution. Use for any multi-step or multi-file task. Triggers: plan this out, write a plan, how would you approach this, break this down, what is the implementation plan, roadmap this.
writing-skills	Create, edit, test, or debug agent skills - SKILL.md frontmatter and body structure, when a skill is warranted, skill types, discovery optimization (the description is the only part always loaded, and it is hard-capped at 500 characters), flowchart usage, and common mistakes. Use whenever authoring or revising a skill, or when a skill is not triggering. Triggers: create a skill, write a skill, edit this skill, my skill is not firing, improve the skill description.