一键导入
draft-structure-outline
Create a structure outline with vertical slices from a design discussion document. Enforces vertical decomposition over horizontal layers.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Create a structure outline with vertical slices from a design discussion document. Enforces vertical decomposition over horizontal layers.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
The skill for "is this AI-written?" or "make this sound more human." Use whenever a specific text sample is in question and the core concern is AI authenticity — student submissions suspected of AI authorship, blog/wiki drafts that feel off, PR commit messages that smell like boilerplate, cover letters that sound robotic, paragraphs an editor flagged. Detects copula avoidance, ChatGPT vocabulary, significance inflation, and 30+ other documented AI tells. Also rewrites flagged sections. Not for grammar checks, summarization, or style edits where AI detection is not the concern.
Chain extract-research-questions into objective-codebase-research. Convenience wrapper for the Q+R phases of QRSPI.
Draft a structured design discussion from research findings. Interactive — presents understanding for corrections before finalizing.
Extract 5-10 codebase research questions from a ticket or description. Questions only — no answers or opinions.
Conduct problem-aware, solution-blind codebase research. Outputs factual findings only — no opinions or suggestions.
Extract one durable lesson from a session into AGENTS.md. Invoke with a session ID to review a past session.
| name | draft-structure-outline |
| description | Create a structure outline with vertical slices from a design discussion document. Enforces vertical decomposition over horizontal layers. |
| allowed-tools | ["Read","Glob","Grep","Write"] |
You are a structure planner. Your job is to decompose a design into vertical slices that each deliver independent value.
Vertical slices only. You must:
You must NOT:
Anti-pattern: "Phase 1: Database schema, Phase 2: API endpoints, Phase 3: UI" — this is horizontal layering. Instead: "Slice 1: User can create a widget (DB + API + UI for create flow)".
Read the design discussion document completely. Identify:
For each slice of user-visible value:
Read references/schema.md for the output structure. Draft the outline (~300 lines, soft target).
Save to the project's thoughts directory (e.g., thoughts/plans/YYYY-MM-DD-topic-slug-outline.md). If no thoughts directory exists, save alongside the design document.
Present the outline and ask for feedback before considering it final.