Michael Ramos

Open the assistant’s latest rendered message in Plannotator and return specific annotations for revision. The skill distinguishes requested edits from approval, approval with notes, and a closed session, so each review result receives the appropriate response.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Annotate the assistant’s latest response for revision
• Approve a response without requesting further work
• Approve with notes to guide subsequent work

Prepare and publish a Plannotator release with contributor credits, coordinated version updates, ordered builds, and tag-triggered publishing. The workflow also checks package contents, security scan results, and evidence showing how release files were built.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Draft release notes with contributor credits
• Update versions consistently across package files
• Check builds and package contents before release

Turn implementation plans, pull request changes, and technical concepts into HTML visual explanations with Plannotator styling. Present diagrams, mockups, and review priorities through an annotation interface, with approval controls for plans and proposals.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Presenting an implementation plan for approval
• Explaining code changes and review priorities
• Illustrating system architecture and data flow

Audit npm dependencies before updating them with Bun. Check maintainers, release age, signatures, published file changes, and release notes, then update packages that pass review and record deferred updates for later follow-up.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Auditing dependency updates before installation
• Checking maintainer changes and suspicious package contents
• Updating packages that pass integrity checks

Use Plannotator to review plans, code changes, documents, and running local apps in a browser. This reference covers returning feedback to agents, browsing past decisions, sharing guided code reviews, and leaving questions for later replies.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing and approving plans or specifications
• Reviewing local code changes or pull requests
• Annotating documents or running local apps

Review code changes in Plannotator’s browser interface and have the agent address returned comments. Choose the current working directory, another checkout, or a pull or merge request URL, with options to focus on a specific comparison base.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review changes in the current working directory
• Review a separate working directory
• Review a pull or merge request by URL

Open documents, text configuration files, HTML, URLs, or folders in Plannotator for browser review. The agent responds to returned annotations and can use an approval session when you need to accept a plan, specification, or document.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding document feedback in a browser
• Reviewing text configuration files or HTML
• Approving a generated plan or specification

Review Markdown files, HTML files, URLs, or folders in Plannotator’s annotation interface. The agent responds to requested changes and distinguishes them from approvals, optional approval notes, and sessions closed without feedback.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a Markdown document
• Collecting comments on HTML or web pages
• Opening a folder for annotation

Turn an idea into a goal package for /goal. Collect decisions through Plannotator, review testable requirements, explore the codebase, and produce an approved execution plan with verification steps and a clear completion condition.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning a rough feature idea into testable requirements
• Agreeing on scope and success criteria before implementation
• Creating an execution plan grounded in the codebase

Open Plannotator’s browser-based code review interface from Kiro and address the returned feedback. Review the current directory, another working directory, or a pull request URL, and optionally choose a comparison base to focus the changes shown.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review code changes from Kiro
• Review a separate working directory
• Open a review for a pull request URL

Open files, folders, or URLs in Plannotator’s annotation interface, then have the agent address the returned comments. Use it to review Markdown, plain-text configuration files, or HTML through a shared feedback workflow.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a Markdown document
• Commenting on configuration files
• Opening a folder for annotation

Review Renovate pull requests that update GitHub Actions. Verify pinned commits against upstream version tags, inspect release notes for breaking changes, and check existing workflow settings before giving a clear recommendation on whether to merge.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing GitHub Actions updates proposed by Renovate
• Verifying pinned commits against upstream version tags
• Checking breaking changes and workflow compatibility

Analyze rejected plans and reviewer feedback to identify recurring concerns, changing expectations, and concrete prompt improvements. Produce an HTML dashboard from Plannotator archives, or use Claude Code plan rejection reasons when those archives are unavailable.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding recurring reasons for plan rejection
• Understanding how review expectations changed
• Deriving planning instructions from past feedback

Bring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in the verification or a bug in the code. Use for /maintain-formal-verification-skill, "is the model still true to the code", or after merges and refactors that touched verified code without rechecking it.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate a project-local skill that formally verifies the code where a bug costs the most and tests reach the least, in any language, with whichever verification tool fits. Use for /create-formal-verification-skill, "model-check this race", "prove this invariant", or when concurrency, retries, state machines, parsers, or unsafe code need more than tests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Sharpen a task before starting: the expert approach, what the user is really after, and the right level of specification. Use for /sharpen.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Restate in your own words what you think the user's goals are and what problem they're trying to solve. Use for /in-your-own-words.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Cut AI tells from any writing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Triage Slack issue reports with one thread-only verdict, evidence review, cause-aware routing, tracker dedupe, and fail-closed ticket creation. Use only from the configured Benny triage automation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes, and open a bounded draft pull request only after before-and-after proof. Use only from the configured Benny repro automation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configure Benny and prepare its triage and repro automations. Use when installing Benny or changing its Slack, tracker, repository, routing, control, model, or budget settings.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.