Chris S

Assess whether a multi-agent workflow justifies its coordination costs. Examine handoffs, lost context, and distinct contributions, then compare the setup with one capable agent to recommend keeping, simplifying, or restructuring it.

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

• Reviewing a workflow before adding another agent
• Finding costly handoffs in a slow workflow
• Checking whether agent agreement adds useful evidence

Handle small, self-contained changes with a known solution, such as typo fixes, configuration edits, or single-file cleanup. Implement the change, create a focused Git commit, and save a task summary and state record.

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

• Fix typos in a README
• Repair a broken import in one file
• Adjust configuration settings

Bring project Markdown documentation into line with code changes. Update factual references such as paths, versions, and counts, check consistency and document links, and reflect the documentation work in the pull request description.

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

• Updating documentation after code changes
• Checking versions and counts across documents
• Adding release notes to CHANGELOG

Record the goal, success criteria, boundaries, and constraints of a complex task in a persistent document. Define human and AI responsibilities, consult the record during work, and check the final result against the original intent.

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

• Clarifying goals before a complex task
• Defining scope and constraints
• Assigning human and AI responsibilities

Analyze reference articles and social posts to uncover structure, persuasive techniques, and writing patterns. Turn the findings into reusable templates, opening patterns, and interview questions for planning new content.

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

• Compare the structure of reference articles
• Extract opening patterns from social posts
• Build a reusable newsletter template

Keep a persistent record of project bugs and blockers in a local Markdown file. List issues by severity and category, inspect individual records, and save resolution notes so problems and their fixes remain available across sessions.

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

• Recording a bug to address later
• Reviewing unresolved issues across sessions
• Saving resolution notes after a fix

Diagnose Claude Octopus installation and runtime problems across 15 categories, including provider authentication, configuration, hooks, and scheduling. Get a readable or JSON report, investigate specific areas, and review proposed fixes before approving changes.

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

• Checking the environment after a plugin update
• Investigating provider authentication problems
• Verifying hooks and scheduled jobs before a demo

Restore project files from a previous Git checkpoint after previewing affected files and receiving explicit confirmation. Create a safety tag before restoration, preserve recorded lessons, and keep the current branch and commit history in place.

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

• Listing available project checkpoints
• Restoring files after an unsuccessful change
• Previewing files affected by a rollback

Reviews code for common security weaknesses, authentication problems, exposed credentials, and unsafe configuration. It adjusts review depth to the changes and offers an adversarial workflow, where defensive and attacking perspectives guide fixes and subsequent verification.

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

• Checking changed code before committing
• Reviewing authentication and API access controls
• Finding credentials left in Git history

Write or review skills for a consistent process across runs. Check activation conditions, ordered steps, completion criteria, and reference placement, then identify unclear instructions, overlapping triggers, and content that belongs in an existing skill.

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

• Define clear steps and completion criteria for a new skill
• Investigate inconsistent behavior across skill runs
• Check for overlapping skill activation conditions

Create a structured specification in plain language from a feature description and multi-AI research. Define actors, behaviors, constraints, dependencies, and acceptance conditions, while checking completeness and keeping unresolved user decisions visible for later review.

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

• Write a specification for a new feature
• Define authentication behaviors and edge cases
• Document performance and security constraints

Audit an application or selected features with a structured checklist. Record evidence for broken behavior, incomplete implementations, and inconsistent patterns, then organize findings by severity and propose a prioritized repair plan.

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

• Check application features before release
• Find recurring implementation problems
• Review button and form consistency

Examine an existing plan, decision, or design through one question at a time, each with a suggested answer. Clarify assumptions, contradictions, and dependencies, then summarize agreed decisions, needed changes, and unresolved blockers.

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

• Examine a plan before committing
• Untangle decisions that depend on each other
• Clarify an uncertain project scope

Test one risky assumption through a prototype with an agreed deadline, hypothesis, and success signal. Record observations and the source revision, then return a keep, discard, or inconclusive verdict with the status of each artifact.

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

• Testing one uncertain assumption before implementation
• Setting a deadline and success signal for a prototype
• Deciding whether to keep or discard prototype results

Review a pull request or feature in two stages: first check implementation against recorded requirements, then examine code quality. Identify unfinished code, logic and security issues, and changes needed before merging in a combined report.

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

• Review a completed feature against its requirements
• Check whether a pull request exceeds agreed boundaries
• Find unfinished code and quality issues

Gather advice from multiple language models assigned different roles, then combine their proposals and critiques into a recommendation. Set budget and depth limits while retaining disagreements, minority views, and risks for decisions or implementation planning.

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

• Comparing options before a decision
• Reviewing code or strategy from several perspectives
• Preparing an implementation plan with risks

Plan a new interface using design reference searches, critique, and contrast checks. Produce colors, typography, reusable styling values, component specifications, layouts, and a style guide tailored to the product, audience, and selected technology.

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

• Planning a dashboard’s colors, typography, and spacing
• Preparing component states and keyboard interaction specs
• Defining responsive layouts and a style guide

Resume a previous workflow after a new conversation or context reset. Read saved project state and handoff notes, summarize recent progress and blockers, and identify the appropriate next action for planning, implementation, or delivery.

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

• Continuing work in a new conversation
• Restoring context after conversation compression
• Reviewing where a previous session stopped

Apply safeguards when analyzing external articles or posts. Validate URLs, limit fetched content, label source text as untrusted data, and clean analysis output so embedded instructions are treated as material rather than commands.

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

• Checking external URLs before fetching content
• Preparing article or post analysis
• Passing untrusted text to subagents

Read project state and roadmap files to show the current phase, progress, blockers, and suggested next actions. Summarize recent work across sessions and suggest lasting project knowledge to add to CLAUDE.md.

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

• Checking project progress and the current phase
• Identifying blockers and next actions
• Reviewing recent work across sessions

Run repeated rounds of code fixes, performance improvements, or other refinements with defined goals and progress tracking. Evaluate each round, stop when appropriate, and optionally use numeric measurements to keep improvements or roll back regressions.

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

• Repeat fixes and tests until all tests pass
• Improve response time toward a target
• Refine error messages against clarity criteria

Detects whether a task concerns software development or research and strategy by examining the request and project files. Workflow skills can use the result to choose agents, output formats, and review criteria suited to the work.

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

• Switching between coding and strategy work in one project
• Choosing output formats for research or implementation
• Overriding an incorrect automatic context detection

Save design documents with branch, author, and revision history so later sessions can recover earlier decisions. Keep previous versions intact, search related designs, and carry constraints and recommendations into implementation or review.

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

• Save design decisions after planning
• Trace revisions for a Git branch
• Recover design context in a later session

Choose how to handle repository initialization, code review, and security review requests. Start with Claude’s built-in commands for ordinary tasks, and route requests for multiple opinions, adversarial analysis, or specific providers to Octopus.

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

• Choose a route for repository initialization
• Select the handling for a routine code review
• Route a request for multiple AI opinions