Turn a development-ready feature's specifications, customer context, demand evidence, and mockups into a concise executive summary. Give sales, leadership, and engineering one shared document covering the problem, solution, key decisions, scope, dependencies, metrics, and audience-specific questions.
中文简介正在准备中。当前显示英语简介。
Generate a 1-2 page executive summary for a feature — orients sales, leadership, and engineering from a single document.
安装前可以查看交给 AI 代理的指令内容。
You generate an executive summary for a feature that's ready for development. The summary orients three audiences from one document: sales (pitch), leadership (strategy), and engineering (behavioral overview).
A single executive-summary.md file in the feature folder. 600-800 words excluding mockups and FAQ. Written in present tense as if the feature already exists.
Before writing, silently gather all context from the feature folder:
---
title: "Executive Summary: [Feature Name]"
feature: [feature-folder-name]
status: [ready | in-progress | shipped]
jira: [ticket key]
updated: [today's date]
---
# [Feature Name]
## The Problem
[2-3 sentences. Customer pain in their language. Name real customers/prospects.]
## The Solution
[2-3 sentences. What we built, present tense. No jargon.]
## Who It's For
[Primary personas + named customers/prospects waiting for this.]
## Why Now
[Deals it unblocks, competitive gap it closes, what it enables next.]
## How It Works
[5-8 key capabilities. Describe actual user-facing behavior — enough for a dev to understand what to build.]
## Key Decisions
[5-8 non-obvious business rules and design choices. Focus on surprising or counter-intuitive ones.]
## Visual Preview
[2-3 ASCII mockup screens from supporting/ — the key screens that tell the story.]
## What We're NOT Building
[5-8 key out-of-scope items with brief reason.]
## Dependencies & Sequencing
[What must ship first. Cross-feature dependencies. Prerequisites.]
## Success Metrics
[2-4 measurable outcomes. Mix of usage and business metrics.]
## FAQ
### For Sales
[2-3 questions. When available, what to tell prospects, competitive positioning.]
### For Leadership
[2-3 questions. Opportunity cost, strategic fit, risks.]
### For Engineering
[2-3 questions. Dependencies, known risks, what's deferred, data model implications.]
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Automate website interactions through a command-line browser tool. Navigate pages, fill forms, extract text, save screenshots or PDFs, reuse login sessions, and compare page states to check the effects of actions or website changes.
中文简介正在准备中。当前显示英语简介。
Design and maintain applications where OpenRig agents help run the system. Organize instructions, shared state, and artifact checks, then trace unexpected behavior to the code, skill, or schema that needs repair.
中文简介正在准备中。当前显示英语简介。
Design and run bounded procedures in environments where current conditions are uncertain. The skill separates agent judgment from precise tool actions, verifies each effect, and records checkpoints so interrupted work can resume from observed evidence.
中文简介正在准备中。当前显示英语简介。
Create reusable starting configurations that combine an agent’s role, startup context, and source history. The skill guides registry entries, checks whether their sources are current, and manages their progression from initial capture to recommendation or retirement.
中文简介正在准备中。当前显示英语简介。
Guides the design and review of agent startup context, including role files and links to authoritative records. It helps identify stale guidance, missing updates, overloaded startup files, and instructions that lose the purpose of the work.
中文简介正在准备中。当前显示英语简介。
Configure selected OpenRig command permissions in Claude Code or Codex at the agreed project or user scope. Preserve existing restrictions, verify that settings load and behave as intended, and record additions so they can be removed later.
中文简介正在准备中。当前显示英语简介。