一键在 Manus 中运行任何 Skill

开始使用

spec

星标22

分支17

更新时间2026年3月17日 21:42

Phase 1 planning — read docs, read source, write implementation plan

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

OpenIPC

OpenIPC/waybeam_venc

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

相关职业SOC

基于 SOC 职业分类

软件开发工程师计算机与数学类职业·SOC 15-1252

SKILL.md

readonly

name	spec
description	Phase 1 planning — read docs, read source, write implementation plan
argument-hint	<task-description>
user-invocable	true
allowed-tools	["Read","Glob","Grep","Bash"]

Phase 1: Spec (Plan)

Before writing any code, produce a plan for the requested change.

Read the relevant documentation in documentation/.
Read every source file you intend to modify.
Write a concise plan:
- What changes and why.
- Which files are affected.
- Any risks or open questions.
Document key design decisions and their rationale. If there are multiple viable approaches, state which one you chose and why. This prevents oscillating between approaches during implementation.
Present the plan and wait for human approval before proceeding.

Do NOT skip to implementation. A good plan lets you one-shot Phase 2.

User request: $ARGUMENTS

同仓库更多 Skills

同仓库

code-review

OpenIPC/waybeam_venc

Adversarial code review — find bugs, style issues, SDK misuse, then challenge findings

2026-03-1722

pre-pr

OpenIPC/waybeam_venc

Pre-PR pipeline — version bump check, changelog, lint, build, and diff summary

2026-03-1722

simplify

OpenIPC/waybeam_venc

Phase 3 review — find unnecessary code, abstractions, and dead paths, then simplify

2026-03-1722

verify

OpenIPC/waybeam_venc

Phase 4 verification — lint check then full dual-backend build verification

2026-03-1722

code-review

OpenIPC/waybeam_venc

Adversarial code review with two passes. First finds issues, then challenges each finding to eliminate false positives. Use before merging.

2026-03-1522

simplify

OpenIPC/waybeam_venc

Review and simplify recent code changes. Remove unnecessary abstractions, dead code, and complexity while preserving behavior.

2026-03-1522

name	spec
description	Phase 1 planning — read docs, read source, write implementation plan
argument-hint	<task-description>
user-invocable	true
allowed-tools	["Read","Glob","Grep","Bash"]

Phase 1: Spec (Plan)

Before writing any code, produce a plan for the requested change.

Read the relevant documentation in documentation/.
Read every source file you intend to modify.
Write a concise plan:
- What changes and why.
- Which files are affected.
- Any risks or open questions.
Document key design decisions and their rationale. If there are multiple viable approaches, state which one you chose and why. This prevents oscillating between approaches during implementation.
Present the plan and wait for human approval before proceeding.

Do NOT skip to implementation. A good plan lets you one-shot Phase 2.

User request: $ARGUMENTS