Milestone progress review — completeness, quality metrics, risk, go/no-go recommendation. At checkpoints or before a deadline.
日本語の概要は準備中です。原文の説明を表示しています。
1.7万 件 ・ 人気順
概要と使いどころ
Milestone progress review — completeness, quality metrics, risk, go/no-go recommendation. At checkpoints or before a deadline.
日本語の概要は準備中です。原文の説明を表示しています。
Turn GDDs plus architecture into epics — one per architectural module, with untraced requirements. Then /create-stories [epic-slug].
日本語の概要は準備中です。原文の説明を表示しています。
Analyze project state, detect stage, identify gaps, recommend next steps. 'Where are we in development?'
日本語の概要は準備中です。原文の説明を表示しています。
Performance profiling — find bottlenecks, measure against budgets, produce ranked optimization recommendations.
日本語の概要は準備中です。原文の説明を表示しています。
Re-evaluate open bugs — priority vs severity, assign to sprints, surface systemic trends. Run when the count grows.
日本語の概要は準備中です。原文の説明を表示しています。
Set up the owner profile so a personal agent knows who it works for (first-run setup, "get to know me"), or distill colleague, relationship, or celebrity source material into reusable Person Profiles for agents.
日本語の概要は準備中です。原文の説明を表示しています。
Build a throwaway prototype to answer how something should work, feel, or read. Use when committing the wrong answer would be expensive to unravel and a cheap sketch cannot settle it. Not a rough visual probe during brainstorming, not for deciding what to build, not polishing a feature that already works, not implementing the real thing.
日本語の概要は準備中です。原文の説明を表示しています。
Generate time-windowed product pulse reports from configured signals.
日本語の概要は準備中です。原文の説明を表示しています。
Explain how and why something has its current shape, or what happened over a window of work, grounded in evidence. Use when the user asks for an explanation. Use ce-pov for a judgment or recommendation.
日本語の概要は準備中です。原文の説明を表示しています。
Review requirements, plans, or specs with role-specific lenses. Use when the user wants to improve an existing planning document.
日本語の概要は準備中です。原文の説明を表示しています。
Explore vague or ambitious ideas into a right-sized requirements-only unified plan. Use when the user wants to brainstorm or scope what to build. Not for executing already-specified work. Use ce-pov for a verdict on adopting a named external technology.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze recorded product feedback into evidence for bugs and requirements. Use when a Riffrec capture or other screen, voice, or notes artifact needs interpretation. Use for Riffrec setup, capture, or sharing help when no recording exists yet.
日本語の概要は準備中です。原文の説明を表示しています。
Develop independent competing solutions to a defined brief, compare them, and synthesize a winning approach. Use when choosing well requires developing alternatives beyond their current form. Use ce-pov to judge developed material and ce-ideate to discover opportunities.
日本語の概要は準備中です。原文の説明を表示しています。
Generate and evaluate grounded ideas. Use when the user wants ideas, improvements, or surprising directions before choosing one to develop. Not for refining an idea they already have (ce-brainstorm) or judging one already on the table (ce-pov).
日本語の概要は準備中です。原文の説明を表示しています。
Commit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.
日本語の概要は準備中です。原文の説明を表示しています。
Draft launch or promotion copy for a shipped feature.
日本語の概要は準備中です。原文の説明を表示しています。
Judge a supplied subject against the project's evidence and constraints. Use when assessing an external-adoption question, a holistic take on a document, or a supplied approach set. Use for an oracle panel to consult other models and reconcile their opinions. Use ce-explain for understanding and ce-doc-review for findings review.
日本語の概要は準備中です。原文の説明を表示しています。
Assess whether furniture fits in a measured Pascal room or layout. Use this skill for sofa, table, bed, cabinet, appliance, staging, placement, collision, clearance, or rotated-footprint questions. Produce a tool-backed spatial report that distinguishes footprint fit from unsupported height, door-swing, assembly, and delivery-route claims, and return insufficient evidence when dimensions or scale are missing.
日本語の概要は準備中です。原文の説明を表示しています。
Open or update a pull request on pascalorg/editor from the current branch, describing only what the branch actually did. Use when the user asks to open/create a PR, push and PR, or ship a branch in the editor repo.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain the slopus/happy open source project. Triage issues, draft closing comments, find duplicates, check if bugs are fixed on main, and engage with community contributors. NEVER posts comments or closes issues without showing exact text and getting approval first.
日本語の概要は準備中です。原文の説明を表示しています。
A user saw internal_error, "Unexpected server error", a 500, or an opaque failure in a shipped OpenWork build. Find the cause from local logs and Sentry, name the regressing PR, file the issue, and reply where it was reported.
日本語の概要は準備中です。原文の説明を表示しています。
Open a PR, write or rewrite a PR description, "the PR body is too long", or check whether a PR description is readable. Use whenever a PR is created or its body is edited.
日本語の概要は準備中です。原文の説明を表示しています。
Workspace guide to introduce OpenWork and onboard new users.
日本語の概要は準備中です。原文の説明を表示しています。
Measure whether the chat jumps while a turn runs by sampling the Working line's position over CDP and counting upward moves. Use when changing step rows, live status lines, folding, or anything that can shrink content during a run.
日本語の概要は準備中です。原文の説明を表示しています。