methodology-process

> Adversarial regulatory-compliance reviewer that maps regulatory obligations, compliance gaps, licensing issues, policy controls, agency guidance, and enforcement-risk scenarios. Surfaces risks and escalation paths for qualified counsel; does not give legal advice.

Use this skill when a Legal or HR agent must hand a matter to another agent and the context, uncertainty, evidence quality, privilege posture, and privacy posture must survive the handoff. It defines the shared legal-hr-case-capsule — a controlled, auditable exchange record with…

Use this skill when a Legal or HR matter must be classified and routed to the right specialist agent, when a matter crosses both domains and needs parallel review, or when Legal and HR agents disagree and the conflict must be resolved. It defines routing rules, the overlap…

This skill defines the **salesforce-case-capsule** — the single structured record that Salesforce specialist agents exchange when a matter crosses an agent boundary. The capsule exists so that no agent works in a silo, no context is lost in a handoff, and every cross-domain…

This skill defines the immediate escalation response path when a Salesforce data exposure event has been detected or is strongly suspected. It exists because exposure events in Salesforce orgs — particularly involving guest users, Experience Cloud, Data Cloud, or Marketing Cloud…

This skill is a refusal-by-default gate for any proposed mutation to a live Salesforce production org. It exists because production org changes carry irreversible risk — data exposure, broken automation, permission widening, and revenue-logic corruption can all result from…

This skill provides the shared vocabulary for classifying Salesforce matters by type, risk tier, and escalation gate. It exists so that all Salesforce specialist agents use consistent terminology when they classify, route, hand off, and escalate matters. It does not assess…

Use this skill when a Salesforce matter must be classified and routed to the right specialist agent, when a matter crosses multiple Salesforce domains and needs parallel review, or when specialist agents disagree and the conflict must be resolved. It defines routing rules per…

Use this skill when triaging HR and employment-relations risk for an enterprise People function — terminations, discipline, performance management, accommodations, leave, wage/hour, worker classification, discrimination, harassment, retaliation, whistleblower reports, layoffs,…

Use this skill when reviewing legal, contractual, regulatory, privacy, litigation, compliance, or risk-governance questions for an enterprise legal function. Trigger when a user provides a contract excerpt, a policy, a compliance question, a privacy-risk question, or a legal…

Build a Minimum Viable Product — scope ruthlessly, ship fast, learn from real users. Use when: planning what to build first, reducing scope to essentials, launching quickly to test assumptions.

Expert guidance for OKR (Objectives and Key Results) planning, helping product teams set ambitious goals, define measurable outcomes, align teams, and run quarterly planning cycles. Applies frameworks from John Doerr (Measure What Matters), Christina Wodtke (Radical Focus), and…

Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when: user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.

Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when: user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".

Expert guidance for writing Product Requirements Documents (PRDs), helping product managers create clear, actionable specs that align engineering, design, and stakeholders. Produces PRDs that define the problem, success metrics, scope, user stories, edge cases, and launch…

Analyze a project and recommend highest-value skills to create or update. Use when: auditing project skills, getting skill recommendations, or reviewing existing skill coverage.

Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when: user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

Apply systems thinking to business problems — identify constraints, understand feedback loops, anticipate second-order effects, and improve processes. Use when: diagnosing why a business process is broken, optimizing operations, understanding complex system behavior.

Scans codebases for technical debt signals and prioritizes them by business impact. Finds TODO/FIXME/HACK comments, outdated dependencies, code duplication, and correlates with git history to identify high-churn debt hotspots. Use when someone asks about technical debt, code…

Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when: user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language,…

Answer questions about any codebase using an AI-generated knowledge graph. Use when: asking architecture questions about a project, understanding how specific features work, exploring codebase relationships interactively.

Launch an interactive web dashboard to visualize a codebase as a knowledge graph. Use when: exploring project architecture visually, seeing file/function dependencies, understanding code structure at a glance.

Analyze git diffs and PRs using the codebase knowledge graph to understand impact and risk. Use when: reviewing pull requests, understanding what a diff actually changes, assessing risk of a code change.

Get a deep-dive explanation of any file, function, or module using the codebase knowledge graph. Use when: understanding unfamiliar code, explaining how a feature is implemented, learning a legacy codebase.

Generate a comprehensive onboarding guide for new developers joining a project, based on the codebase knowledge graph. Use when: onboarding new team members, creating developer documentation, ramping up on a new project.