team

Plugin team from marketplace andymai in andymai/skills. Commands read from the repo's manifest — 2 days ago.

Skills (3)

• obsidian-project

  Start a new project in an Obsidian vault. It writes one folder of prefix-named notes (overview, PRD, architecture, research, tasks), links them, and adds the project to the vault's index. Use when the user asks to start, set up, or scaffold a project, a project folder, or project docs in Obsidian or

• outward-writing

  Write outward-facing prose another person will read: a design or shaping doc, a proposal, a wiki page, a Slack message, a PR title, body, or reply, a review reply, an issue or ticket, an email. You collect every fact with a source, write the draft in ASD-STE100 Simplified Technical English, fact-che

• shepherd-pr

  Drive the current branch's pull request to a fully clean state — every review comment resolved, every check-run green (including neutral-status reviewers that the CI rollup hides), and CI passing — running as an autonomous loop, then hand the PR back. Use when the user says "shepherd the PR", "drive

Slash commands (8)

• /team:audit-claudemd

  Audit or bootstrap the project's CLAUDE.md against observed conventions

• /team:branch

  Create a branch following <type>/<kebab-description> naming

• /team:check

  Run the project's local quality gate (fmt + lint + types + tests)

• /team:commit

  Create a conventional commit from working tree changes

• /team:contribution-report

  GitHub contribution summaries for performance reviews

• /team:pr-description

  Generate a PR title and description from branch changes

• /team:upgrade-dep

  Upgrade a dependency and fix breaking changes

• /team:worktree

  Set up a git worktree under .worktrees/ for parallel branch work

Subagents (6)

• debugger

  Systematically investigates bugs by reproducing, isolating, and root-causing issues, then writing verified fixes. Use when something is broken and you need to find out why.

• engineer

  Implements features and their tests by deeply understanding existing codebase patterns and conventions, then writing clean code that integrates seamlessly with the established architecture. Writes the failing test first for a bug fix.

• gap-finder

  Finds missing pieces — either by comparing implementation against a spec, or by analyzing the diff for orphaned references, broken patterns, and incomplete state flows. Use after engineering work and before code review.

• optimizer

  Simplifies and refines recently modified code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recent changes unless instructed otherwise. Makes confident, high-impact improvements without over-engineering.

• researcher

  Conducts deep technical research by exploring codebases, tracing patterns, comparing technologies, and synthesizing findings from documentation and the web into actionable insights with cited sources

• reviewer

  Reviews code for bugs, logic errors, security vulnerabilities, and adherence to project conventions, using confidence-based filtering to report only high-priority issues that truly matter

Similar plugins