'first run' 검색 결과

Spawns full Claude Code peer sessions in separate terminal panes and git worktrees, real sessions rather than subagents, each with a directed task and contract brief, monitored and merged by the spawning lead. Detects the environment and uses herdr first, then tmux, then a native claude background agent. Use when work must persist or run beside the current session, needs a separate worktree or permission settings, should remain user-steerable in a visible pane, or when the user asks to spawn, hand off, or parallelize full sessions. Also spawns Codex peers into those panes. Excludes bounded consults and subagent-scale work.

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

Checks whether each claim in a manuscript is supported by the source it cites, reading the project's per-source Markdown knowledge base. Flags contradicted, unsupported, overclaimed, out-of-scope, and misattributed claims with verbatim source quotes. Runs citation-check first, and stops at a pre-flight gate when the knowledge base is missing, incomplete, or holds unconverted PDFs. Use to verify that a draft's claims match the sources it cites.

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

ACCESS-GATED beta. Deepline Monitors are provider event feeds (job posts, email replies, funding, intent) that stream into your warehouse and trigger plays. Only use if you have monitor access: run `deepline monitors status` first; if it reports no access, do NOT use this recipe — tell the user to contact the Deepline team.

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

Evaluate and iterate on the SDLC Layer Separation Architecture implementation. Runs validation checks (cross-references, doc completeness, layer metadata, integration points), produces a findings report, and supports iterative fixes. Use when validating first-pass implementation, before claiming layer work is complete, or when improving layer docs/schema.

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

Shapes for running many sub-agents at once — fan-out with a barrier, maker/checker, generate-and-filter, tournaments for ranking, hypothesis fan-out for root cause, and loops that stop on a condition with a cap. Use when a phase has several independent targets, when a task is too large or too repetitive for one window, when the same edit applies across many files, when ranking or judging a large set, when several hypotheses compete, or when work must repeat until a signal says stop. Does not apply when units depend on each other's results or the cause is still unknown — investigate first, then parallelize.

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

Value investing analysis using Graham (NCAV/net-net/defensive-investor) and Buffett (economic moat/ROE/FCF) methodologies. Covers single-stock diagnostics and batch screening for both Graham cigar-butt and Buffett quality-compounder criteria. Runs cross-statement reconciliation before scoring. Data from Longbridge CLI first, MCP fallback, WebSearch only for genuine gaps. Triggers: "格雷厄姆", "巴菲特", "捡烟蒂", "烟蒂股", "NCAV", "净流动资产", "护城河", "价值投资", "安全边际", "深度价值", "撿煙蒂", "煙蒂股", "淨流動資產", "護城河", "安全邊際", "Graham", "Buffett", "cigar butt", "net-net", "NCAV screen", "moat", "value investing", "margin of safety", "deep value", "quality compounder", "價值投資", "深度價值", "防御型投资者", "防禦型投資者"

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

Investigate an alert, page, or production symptom in an incident channel or a team's oncall / monitoring channel, and report findings a human can verify. Ordinary conversation and chatter are not alerts; leave those alone. Use when an alert or page lands, when error rate, latency or saturation is up, when someone asks "why is X broken", "investigate", "what changed", "root cause this", pastes a monitor, dashboard, trace or error-tracker link, or reports production trouble; also by default when an alert lands in a covered channel unasked. Feed-level asks land here too ("which alerts matter", "triage today's alerts"), plus the scheduled alert-review routine and the ticket path ("customer X can't check out"). Runs a fast first pass posted as a short interim update with a TL;DR, every finding carrying the query or link to verify it, then proposes the fix and — with connector access and confirmation — carries it out, never unattended. Afterwards `incident-postmortem` writes it up.

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

Evidence-first marketing audit of a third-party local business (café, roaster, shop, restaurant, hotel, clinic, home service) from a Google Maps, share.google or website link — located DataForSEO rankings, map packs, search volume and seasonality, listings, reviews, backlinks, AI-assistant answers and a site crawl, plus direct checks (real-browser access, page weight, store shipping quotes, email DNS, mobile screenshots) — delivered as an owner-facing report with priced offers, an exact change list and a 12-week plan, optionally localized and bilingual. Use when "audit this business", "full marketing audit of <business>", "prospect audit", "local business audit", "use DataForSEO for the hard SEO data", "go deeper", "rerun it for local <market>", "also in Spanish", "give me the offers, changes and 3 month plan", or a business link arrives with "audit". For auditing your own product across channels use /kai-audit.

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

First-run guided setup for a fresh gAIOS clone. Interviews the user (identity, role, priorities, voice, connections, team, pain, guardrails) and fills the templates — CLAUDE.md, context/, references/voice.md, connections.md — then introduces the WAT / wiki / workflows / experiments features. Trigger on "/setup", "set me up", "get started", "onboard me", or a fresh clone where CLAUDE.md still has {{placeholders}}.

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

Use when the user brings any fuzzy, half-formed, or interrupt-driven input — an order from a boss, a forwarded email thread, a ticket, a chat message, a "can you look into X", a raw idea — and it needs framing before work starts. Turns the input into a structured brief (Context · Desired outcome · Goal · Owner · Next step · Decision needed). This is the AIOS's front door; run most things through it first. Trigger on "/structure", "frame this", "what's the actual ask here", "structure this", or any vague task that lacks a defined outcome.

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

OctoClaw is the TypeScript-first policy, delegation, status, and operator layer for OpenClaw. Use it when a turn should be routed through reply/delegate policy, WorkContract-backed delegation, runtime status, IM delivery, or feedback-loop tooling.

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

Test a product concept with Amazon's Working Backwards method: write the press release for the finished product first, then answer hard customer and stakeholder questions, ending in a complete PRFAQ document. Use when the user requests to 'create a PRFAQ', 'work backwards', or 'run the PRFAQ challenge'

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

Step-by-step installer for the stitch-kit plugin and Stitch MCP server. Use this when setting up the plugin for the first time, diagnosing connection issues, or helping a new user get Stitch running in Claude Code or Codex CLI.

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

Phase 5 of 5 — triage-first review orchestrator; dispatches up to 17 domain checks in parallel and compiles one report. Use only when the user asks to run Phase 5 or review a PR, branch, or set of changes — never trigger automatically after writing code.

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

Build and analyze discrete or continuous Markov chains including transition matrix construction, state classification, stationary distribution computation, and mean first passage times. Use when modeling a memoryless system with observed transition counts or rates, computing long-run steady-state probabilities, determining expected hitting times or absorption probabilities, classifying states as transient or recurrent, or building a foundation for hidden Markov models or reinforcement learning MDPs.

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

Create general-purpose Dockerfiles for Node.js, Python, Go, Rust, and Java projects. Covers base image selection, dependency installation, user permissions, COPY patterns, ENTRYPOINT vs CMD, and .dockerignore. Use when containerizing an application for the first time, creating a consistent build/runtime environment, preparing an app for cloud deployment or Docker Compose, or when no existing Dockerfile is present in the project.

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

Trains the HUMAN user's critical thinking through four modes: drill (argument-analysis items with a single defensible answer, judge stance), scene (Socratic exploration of synthetic scenes or user-supplied material, no verdicts on interpretations; includes a configure track — design the information request and verification plan for a decision before any analysis), expedition (guided audit of impossible-tier problems from verified packs), and detective (a runtime-generated multi-layer case worked as an escape room, guide-and-judge stance). Use when the user wants to practice critical thinking, analyze arguments, hunt assumptions, examine bias, train reasoning, or decide what information a decision needs first. Triggers: critical thinking practice, train my thinking, drill, scene, byom, configure, information plan, what would I need to know, spot manipulation tactics, scam literacy, 批判思考練習, 話術辨識, detective, 查案, 破案, 偵探.

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

Onboarding workflow for cross-library KB query in a consulting practice. Discovers existing user-scope library registrations, prompts for additions, validates each library, helps activate the relevant ones for the current project, runs a smoke test, and reports a clear "ready" or "issues to fix" verdict. Use --verify-only to skip prompting and just validate existing setup (sub-task 23 of

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

Validated Google Play release — runs the pre-flight checks and clears the Play policy gates, builds a signed app bundle with a git-stamped versionCode, uploads to a track, and walks staged rollout (with halt/roll-forward). Use when releasing an Android app to Play.

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

Initialise a project for knowledge base use. Appends the [Knowledge Base] section to the project's CLAUDE.md, creates the library/ directory structure, optionally seeds with three example library files from the Agentic SDLC research, and reports next steps. Run once after installing sdlc-knowledge-base.

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

Validated commit — runs quick checks before committing. Use when ready to commit changes.

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

Run a Programme phase gate validator (requirements / design / test / code) against docs/specs/<feature-id>/. Block on missing artefact or broken cross-phase reference.

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

Generate a GitHub Actions workflow for Android — JDK + Gradle caching, build, unit + instrumented tests, Android Lint, run the Android pre-flight checks, and (optionally) sign + upload a signed app bundle to a Play track. Use when setting up CI for an Android app.

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

Run the SDLC validation pipeline using direct tool invocations. No wrapper scripts required. Use when checking code quality before commits or PRs.

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