メニュー
Four-stage spec-driven development workflow for building new features. Use when the user asks to start building a new feature, begin a development sprint, or wants a structured approach to implement a major component.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
浏览器环境配置技能 - 自动检测系统已安装的 Chrome/Chromium，或提供下载安装指引。支持 Linux/macOS/Windows 跨平台检测。
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of "Word doc", "word document", ".docx", or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a "report", "memo", "letter", "template", or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
使用 Bun.fetch 进行 HTTP API 调用。支持 GET/POST/PUT/DELETE、JSON 处理、请求头设置、超时控制。当用户需要调用 API、获取网络数据、测试 API 接口时使用。
| name | spec-driven-dev |
| description | Four-stage spec-driven development workflow for building new features. Use when the user asks to start building a new feature, begin a development sprint, or wants a structured approach to implement a major component. |
Each stage requires human confirmation before proceeding to the next.
Development Progress:
- [ ] Stage 1: Requirement Clarification
- [ ] Stage 2: Technical Design
- [ ] Stage 3: Plan-Driven Execution
- [ ] Stage 4: Living Doc Backfill
Goal: Transform vague wishes into a concrete feature list.
Actions:
Output format:
## Feature: [Name]
### Core Capabilities
- [ ] Capability 1: [description]
- [ ] Capability 2: [description]
### Dependencies
- Requires: [existing module X]
- Blocked by: [nothing / module Y not yet implemented]
### Risks & Open Questions
- Risk 1: [description]
- Question 1: [need user input on ...]
STOP: Present to user for review. Only proceed after confirmation.
Goal: Produce an Implementation Plan that defines the architecture.
Actions:
docs/architecture_spec.md with new module placementdocs/api_spec.md with interface definitionsOutput format:
## Implementation Plan: [Feature Name]
### Architecture Impact
[Mermaid diagram showing where this fits]
### Interface Definitions
[Go interface code blocks]
### Files to Create
- `internal/xxx/xxx.go` - [purpose]
- `internal/xxx/xxx_test.go` - [test scope]
### Files to Modify
- `cmd/gopherpaw/main.go` - [what changes]
### Execution Order
1. [First task]
2. [Second task]
...
STOP: Present to user for review. This is the "Tech Review" gate. Only proceed after approval.
Goal: Implement feature according to the approved plan.
Execute the plan step by step:
go test ./...Track progress using the execution order from Stage 2. Mark each step as complete.
Rules during execution:
Goal: Ensure all documentation matches the final implementation.
Actions:
docs/architecture_spec.md matches actual imports and dependenciesdocs/api_spec.md matches actual interface definitions in codeCONTEXT.md with new progress statusOutput: summary of documentation changes made.