3,874 件 ・ 関連度順
概要と使いどころ
Use when the user asks to generate, update, refresh or verify project documentation, or to check that docs still match the codebase. Writes up to 9 doc files, each verified against real paths; supports --force and --verify-only.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user invokes /coco or /coco!, says catch me up, or asks what needs attention, a project status, their todos, decisions or people. Renders the PM dashboard and routes each subcommand to its platform tool or a PM skill.
日本語の概要は準備中です。原文の説明を表示しています。
Build and validate .arch/index.json — a committed map from each architectural component of this repository to the real directories and files that implement it, pinned to a git commit, with every path verified to exist. Also detects structural drift between that index and the current code. Use when asked to map a codebase, produce a component or code-ownership index, find which files implement a component, check whether architecture docs are stale, or detect architecture drift after a refactor. Triggers include 'map the codebase', 'component index', 'which files implement X', 'is the architecture still accurate', 'architecture drift', 'refresh the architecture index'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when finished work needs to reach a coco-managed repository (coco-research/coco or similar) — verifies branch state, commits, pushes through the corporate DLP guard only when actually needed, opens a PR against main, waits for CI, and reports the result. Never merges, never pushes to main directly.
日本語の概要は準備中です。原文の説明を表示しています。
Audit and improve the prompt surface of Avibe Agents across backends (Claude, Codex/GPT, OpenCode) — global and project rules, Agent system prompts, Skills, delegation briefs, and Task and Watch messages — using real run evidence. Use when an Agent misbehaves (stalls, over-asks, over-reaches, ignores or over-applies a rule), after a model or backend change, or when the user asks to review, clean up, or tighten prompts.
日本語の概要は準備中です。原文の説明を表示しています。
Weekdays, conditional browser lane. Selects from the ticket ledger hardest first, meaning by severity and then by age within severity, and writes each customer a reply into a dated queue file the member reads, edits, and sends by hand. Where the right answer is a refund, a credit, a plan change, or a cancellation, it names the remedy, the exact amount, and the exact screen, and leaves the granting to the member. It sends only where you released the channel, never posts, never resolves a ticket, spends only where you released it, and never touches a credential.
日本語の概要は準備中です。原文の説明を表示しています。
Weekdays, heavy browser lane, two halves in one run. First it reads the member's own mailbox for replies on the threads the ledger says were sent and records them. Only then does it work out who is due a follow up, write each one into a dated queue file, and compose it into the mailbox as an unsent draft. It holds every outbound action unless you released the channel, and it never touches a credential.
日本語の概要は準備中です。原文の説明を表示しています。
Weekdays, file work only, no browser at all. Walks every AI Employee installed on this machine, reads each one's own run log strictly read only, classifies every routine as running, stopped loudly, stopped silently, or paused, ages the faults, folds the decision register, and writes the one short brief the member opens first. It never writes into another Employee's folder, sends only where you released the channel, spends only where you released it, and never touches a credential.
日本語の概要は準備中です。原文の説明を表示しています。
Weekdays, file work only, no browser at all. Takes the single highest ranked open fault on the fleet and turns it into something the member can act on in a minute: the fault in one sentence, the first record that shows it, what changed around that date, three ranked causes each with its evidence line, what the failure has cost, and one paste ready correction line with the exact path it belongs in. It reads other Employees strictly read only, writes nothing outside its own folder, sends only where you released the channel, spends only where you released it, and never touches a credential.
日本語の概要は準備中です。原文の説明を表示しています。
Weekdays, conditional browser lane. Reads the ticket ledger and the account, billing, and usage surfaces the member named, and decides which paying customers are about to leave. Every flag is a dossier carrying the trip wires that fired, the exact evidence behind each one, that account's whole history, and one suggested save with its cost and the screen it happens on. It reads billing screens and touches no control on them: a refund, a credit, a plan change, and a cancellation are named and never made.
日本語の概要は準備中です。原文の説明を表示しています。
Weekly, browser heavy, read only on every screen. Fixes a scoring window that neither double counts nor loses an hour, reads the member's search performance console and analytics property, verifies each range actually applied before reading a figure, reconciles every number against what this Employee published, writes the week's scoreboard and the short rolling state file every other routine reads, and files what it found as cards rather than doing the work itself. It types nothing on any screen, changes no setting, publishes nothing, and never touches a credential.
日本語の概要は準備中です。原文の説明を表示しています。
Weekdays, heavy browser lane. Reads the member's own signal sources and saved searches, captures dated buying signals together with the contactable people attached to them, and appends both to the ledgers the outreach queue reads. Read only on every people surface, LinkedIn included. It holds every outbound action unless you released the channel, and it never touches a credential.
日本語の概要は準備中です。原文の説明を表示しています。
Weekdays. Turns the contactable people in the signal ledger into today's due first touches and follow ups, written into dated queue files the member reads, edits, and sends by hand, and optionally into the member's own mailbox as unsent drafts. It holds every outbound action unless you released the channel, and it never touches a credential.
日本語の概要は準備中です。原文の説明を表示しています。
Weekdays, browser only when the card needs one. Takes the next ready cards off the launch board and does the work each one names: stages copy into the dashboard, fills a directory or press form and leaves it open in its tab, verifies a setup, packages a handoff, or researches its own next targets. It ticks its own card the moment it has verified the file that closes it. It submits only where you released the channel, sends only where you released the channel, spends only where you released it, and never touches a credential.
日本語の概要は準備中です。原文の説明を表示しています。
Weekdays, heavy browser lane. Reads the member's own saved searches and the named sources for one buyer segment, captures candidate accounts together with the contactable people attached to them, scores every row against the named tests in the qualification file, and writes each one with the evidence that qualified it. Read only on every people surface, LinkedIn included. It holds every outbound action unless you released the channel, and it never touches a credential.
日本語の概要は準備中です。原文の説明を表示しています。
Weekly, on a Friday, read only everywhere. Scores the week from the daily metrics ledger alone, with the screen and the date range beside every number, then writes the ranked paste ready list of what to change in the account next week. Each line names one change, the exact screen, the current value, the proposed value, and the evidence row it came from. It proposes no change it cannot source, it names no action it took because it takes none, and it spends only where you released it.
日本語の概要は準備中です。原文の説明を表示しています。
Weekly. Audits the paid and measurement setup the member already has by reading it, then assembles the parts that are missing as local files: campaign structure, ad copy, negative keyword seeds, and conversion tracking specifications, each one complete and ready to paste. It creates nothing in an account, saves nothing, activates nothing, and spends nothing, unless you released the channel. This is where the spend stop lives.
日本語の概要は準備中です。原文の説明を表示しています。
Teaches agents how to run a timeboxed spike - throwaway code that validates one assumption before DESIGN
日本語の概要は準備中です。原文の説明を表示しています。
Wave methodology knowledge for the buddy agent — what each wave does, its inputs and outputs, and how to route questions.
日本語の概要は準備中です。原文の説明を表示しています。
7 agentic design patterns with decision tree for choosing the right pattern for each agent type
日本語の概要は準備中です。原文の説明を表示しています。
Turn a complete beginner's app idea into a buildable plan, then keep them oriented while they build. Use it whenever someone who has never coded wants to build or "vibe code" an app, has an idea but no idea where to start, or wants it turned into a plan, MVP scope, tech stack, user flows, or blueprint. It has three on-ramps: the full journey, a validate-only pass ("is my idea worth building", "reality-check this idea"), and a plan-only path for someone arriving with validation done ("I already validated my idea", "I have the research, just plan my MVP", "skip the research"). ALSO use it when a non-coder needs build-time basics: what Git and GitHub are, making an account, "commit and push," local vs. staging vs. production, putting an app online (deploy/ship), or keeping API keys safe. AND use it in Checkup Mode when someone who built with AI says it became a mess, the AI keeps breaking things or going in circles, they're scared to touch their code, or they ask "is my code organized" or "can you clean it up." Built for people who don't know what an API, database, or GitHub is, so reach for it when they never say "plan" or "architecture." Not for an experienced dev debugging, refactoring, or setting up CI/CD.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a PERSONAL brand needs to make money — three funnel versions for founder, coach, and creator, an offer ladder from free to low to mid to high ticket, pricing psychology, inbound versus outbound outreach, and brand deal and sponsorship negotiation, with tax and legal variants for US LLC, EU per country, SEA Pte Ltd, and LATAM MEI. Trigger on 'monetize my personal brand', 'offer ladder', 'launch my course', 'coaching packages', 'sponsorship rates', 'I have an audience and no income'. Not for — a company product offer, see `31-offer-design-global` and `17-pricing-strategy-global`; the strategy that comes first, see `23-personal-brand-strategy-global`; running the community, see `28-community-building-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Dung khi sap ra mat san pham, dich vu hoac khoa hoc MOI va can duong di ra thi truong — chon phan khuc beachhead, thong diep launch, kenh theo tung giai doan pre-launch, launch, post-launch, milestone va tieu chi go/no-go. Kich hoat khi user nhac 'go-to-market', 'GTM', 'ke hoach ra mat san pham', 'launch plan', 'tung san pham moi', 'san pham sap ra ma chua biet ban cho ai', 'ra mat khoa hoc moi', 'vao thi truong moi'. Khong dung cho — checklist va war-room dieu phoi ngay launch thi dung skill 60-launch-playbook; ke hoach marketing dinh ky ca ky thi dung skill 00-ke-hoach-mkt; chot dinh vi truoc do thi dung skill 58-positioning.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a launch needs a repeatable EXECUTION playbook — a T-30 to D+7 timeline, per-function checklists for content, design, ads, sales, and engineering, a launch-day war room, an escalation matrix, and roll-back criteria. Trigger on 'launch playbook', 'launch checklist', 'launch day plan', 'launch SOP', 'war room', 'we launch in two weeks and nothing is organized'. Also use when a GTM strategy exists and nobody knows who does what on the day. Not for — the strategy and beachhead choice, see `59-go-to-market-global`; the campaign brief, see `02-campaign-brief-global`; the post-launch review, see `63-campaign-retrospective-global`; a live crisis, see `66-crisis-playbook-global`.
日本語の概要は準備中です。原文の説明を表示しています。