Deep Plan
piercelamb/deep-plan
Creates detailed, sectionized, TDD-oriented implementation plans through research, stakeholder interviews, and multi-LLM review.
A skill your agent uses when 已有经批准的设计/规格说明、多步骤实施任务，在动代码之前需要可执行任务清单时。触发场景：写实施计划、拆解开发任务、implementation plan、执行计划文档、任务拆分、按 TDD 步骤写计划。
Install Writing Plans
$ npx skills add ProgrammerAnthony/Expert-Coding-Harness --skill writing-plans -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ProgrammerAnthony/Expert-Coding-Harness writing-plans --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ProgrammerAnthony/Expert-Coding-Harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/writing-plans .claude/skills/writing-plans && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "writing-plans" agent skill from https://github.com/ProgrammerAnthony/Expert-Coding-Harness/tree/master/skills/writing-plans into .claude/skills/writing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-plans", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ProgrammerAnthony/Expert-Coding-Harness/tree/master/skills/writing-plansType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ProgrammerAnthony/Expert-Coding-Harness --skill writing-plans -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ProgrammerAnthony/Expert-Coding-Harness writing-plans --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ProgrammerAnthony/Expert-Coding-Harness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/writing-plans .agents/skills/writing-plans && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "writing-plans" agent skill from https://github.com/ProgrammerAnthony/Expert-Coding-Harness/tree/master/skills/writing-plans into .agents/skills/writing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-plans", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ProgrammerAnthony/Expert-Coding-Harness --skill writing-plans -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ProgrammerAnthony/Expert-Coding-Harness writing-plans --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ProgrammerAnthony/Expert-Coding-Harness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/writing-plans .cursor/skills/writing-plans && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "writing-plans" agent skill from https://github.com/ProgrammerAnthony/Expert-Coding-Harness/tree/master/skills/writing-plans into .cursor/skills/writing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-plans", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ProgrammerAnthony/Expert-Coding-Harness.git --path skills/writing-plans--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ProgrammerAnthony/Expert-Coding-Harness --skill writing-plans -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ProgrammerAnthony/Expert-Coding-Harness writing-plans --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ProgrammerAnthony/Expert-Coding-Harness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/writing-plans .gemini/skills/writing-plans && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "writing-plans" agent skill from https://github.com/ProgrammerAnthony/Expert-Coding-Harness/tree/master/skills/writing-plans into .gemini/skills/writing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-plans", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ProgrammerAnthony/Expert-Coding-Harness writing-plansInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ProgrammerAnthony/Expert-Coding-Harness --skill writing-plans -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ProgrammerAnthony/Expert-Coding-Harness.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/writing-plans .github/skills/writing-plans && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "writing-plans" agent skill from https://github.com/ProgrammerAnthony/Expert-Coding-Harness/tree/master/skills/writing-plans into .github/skills/writing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-plans", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ProgrammerAnthony/Expert-Coding-Harness --skill writing-plans -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ProgrammerAnthony/Expert-Coding-Harness writing-plans --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ProgrammerAnthony/Expert-Coding-Harness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/writing-plans .opencode/skills/writing-plans && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "writing-plans" agent skill from https://github.com/ProgrammerAnthony/Expert-Coding-Harness/tree/master/skills/writing-plans into .opencode/skills/writing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-plans", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
writing-plans- GitHub stars
- 235
- Token cost
- ~876 tokens
- SKILL.md length
- 121 words
- Files
- 3 (incl. references)
- Skills in repo
- 23
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when 已有经批准的设计/规格说明、多步骤实施任务，在动代码之前需要可执行任务清单时。触发场景：写实施计划、拆解开发任务、implementation plan、执行计划文档、任务拆分、按 TDD 步骤写计划。
- Works in 3 steps: 规格覆盖： 设计文档中的每条需求能否对应到某一任务？漏项则补任务。 → 占位扫描： 对照上一节，搜 TODO、适当、类似 等红线词并修正。 → 命名一致： 后文出现的函数名/类型名是否与前面任务一致。
- 已有经批准的设计/规格说明、多步骤实施任务，在动代码之前需要可执行任务清单时。触发场景：写实施计划、拆解开发任务、implementation plan、执行计划文档、任务拆分、按 TDD 步骤写计划
- SKILL.md covers Inputs / Outputs / Gates /…, 范围检查, 文件结构先行 and 任务粒度, plus 7 more sections
- Calls npm, go and cargo
What it does
Writing Plans is an agent skill from ProgrammerAnthony/Expert-Coding-Harness. Use when 已有经批准的设计/规格说明、多步骤实施任务，在动代码之前需要可执行任务清单时。触发场景：写实施计划、拆解开发任务、implementation plan、执行计划文档、任务拆分、按 TDD 步骤写计划。
Its SKILL.md is about 880 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/plan-document-reviewer-prompt.md` and `references/plan-template.md`).
It sits in Agent Workflows, covering Planning and Test-driven development. The repository describes itself as: 生产级 AI Agent 技能集，辅助AI Harness应用于企业开发，覆盖代码审查、代码安全审计、TDD、需求工程、实施计划与子代理编排、架构设计、调试、前端开发与技能创建全流程。 The licence is MIT.
When your agent uses it
- 已有经批准的设计/规格说明、多步骤实施任务，在动代码之前需要可执行任务清单时。触发场景：写实施计划、拆解开发任务、implementation plan、执行计划文档、任务拆分、按 TDD 步骤写计划
- Tasks that involve Planning
- Tasks that involve Test-driven development
Example prompts
- “/writing-plans”
Requirements
- Python 3
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- 规格覆盖： 设计文档中的每条需求能否对应到某一任务？漏项则补任务。
- 占位扫描： 对照上一节，搜 TODO、适当、类似 等红线词并修正。
- 命名一致： 后文出现的函数名/类型名是否与前面任务一致。
What it can do on your machine
Read from SKILL.md and the folder at commit ab0b827. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npmgocargo
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Writing Plans loads about 876 tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 31 tokens; SKILL.md has 121 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ProgrammerAnthony/Expert-Coding-Harness at commit ab0b827, republished under its MIT licence (© ProgrammerAnthony). 121 words, ~876 tokens.
Download SKILL.mdSave it as
.claude/skills/writing-plans/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- writing-plans
- description
- Use when 已有经批准的设计/规格说明、多步骤实施任务，在动代码之前需要可执行任务清单时。触发场景：写实施计划、拆解开发任务、implementation plan、执行计划文档、任务拆分、按 TDD 步骤写计划。
实施计划编写
在已获用户批准的设计文档（例如方案设计师产出的 docs/specs/…-设计.md）基础上，编写可交给代理或工程师逐步执行的实施计划。假设执行者对代码库与领域几乎零上下文、测试习惯一般：计划中必须写明路径、命令、完整代码块与预期输出。遵循 DRY、YAGNI、TDD、小步提交。
开场声明：「我正在使用实施计划编写技能生成实施计划。」
保存路径（默认）： docs/specs/plans/YYYY-MM-DD-<功能简述>.md
（若用户或项目已有约定路径，以约定为准。）
可选上下文： 大功能建议在独立分支或 git worktree 上实施；若用户未准备，在计划头注明即可，不阻塞写计划。
Inputs / Outputs / Gates / Handoffs（统一契约）
- Inputs（最小输入）：已获批准的设计/规格说明（路径 + 核心需求 + 约束）；目标仓库与测试/运行命令（如
pytest/npm test/go test等）。 - Outputs（产物形态）：一份可勾选、可交接执行的实施计划（结构参考
references/plan-template.md）。 - Gates（继续前必须满足）：
- 禁止占位词（
TODO/TBD/适当/稍后补充），每步必须可执行（路径/命令/预期输出齐全）。 - 需要用户确认的决策点必须显式列出并暂停等待。
- 通用门控清单可复制使用：
../code-review-expert/references/quality-gates-checklist.md。
- 禁止占位词（
- Handoffs（推荐下游）：
subagent-driven-development（子代理驱动开发）：按计划逐任务执行code-review-expert（代码审查专家）：最终质量门禁/收尾审查tdd-master（TDD 开发大师）：执行阶段遵循 RED-GREEN-REFACTOR 节奏
范围检查
若规格仍包含多个可独立交付的子系统，应退回方案阶段拆成多份子规格；若未拆，则建议多份实施计划（一子系统一份），每份计划都能单独产出可运行、可测试的软件。
文件结构先行
在写任务前，先列出将创建/修改的文件及职责，作为分解依据：
- 边界清晰、接口明确；单文件单职责；相关变更放在相近位置（按职责而非按技术层硬拆）。
- 在存量代码库中遵循既有模式；若当前修改的文件已臃肿，可在计划中包含合理拆分步骤。
任务粒度
每一步对应一个可完成动作（约 2–5 分钟）：
- 「编写失败测试」一步
- 「运行并确认失败」一步
- 「写最小实现使测试通过」一步
- 「运行并确认通过」一步
- 「提交」一步
计划文档头部（必填）
每一份计划必须以如下头部开头：
# [功能名] 实施计划
> **给代理执行者：** 推荐配合 `subagent-driven-development（子代理驱动开发）`（每任务独立子代理 + 两阶段审查）或在本会话内按勾选逐步执行并在批次节点与用户确认。任务使用 `- [ ]` 勾选跟踪。
**目标：** [一句话说明交付什么]
**架构要点：** [2–3 句]
**技术栈：** [主要语言/框架/测试命令]
**关联设计文档：** `docs/specs/…-设计.md`（路径按实际填写）
---任务块模板
### 任务 N：[组件或主题名]
**涉及文件：**
- 新建：`exact/path/to/file.py`
- 修改：`exact/path/to/existing.py`（可注行号范围）
- 测试：`tests/exact/path/to/test_xxx.py`
- [ ] **步骤 1：编写失败测试**
```python
def test_具体行为():
result = function(输入)
assert result == 期望
```
- [ ] **步骤 2：运行测试确认失败**
运行：`pytest tests/path/test.py::test_具体行为 -v`
预期：失败（例如 NameError / 断言失败，写明预期信息）
- [ ] **步骤 3：最小实现**
```python
def function(输入):
return 期望
```
- [ ] **步骤 4：运行测试确认通过**
运行：`pytest tests/path/test.py::test_具体行为 -v`
预期：通过
- [ ] **步骤 5：提交**
```bash
git add …
git commit -m "feat: …"
```（语言与测试命令按项目替换：如 npm test、go test、cargo test 等。）
禁止占位（计划不合格）
以下情况禁止出现在最终计划中：
TBD、TODO、稍后补充、实现时再想- 「适当错误处理」「补充校验」「覆盖边界」等无具体代码/断言的描述
- 「为上述编写测试」但无测试代码
- 「同任务 M」（执行者可能乱序阅读——重复粘贴必要内容）
- 只描述动作不给代码块（凡涉及改代码的步骤必须有代码或 diff 级说明）
- 引用未在前文任务中定义的类型/函数/模块
自检（主代理自行完成，不必派子代理）
写完计划后快速过一遍：
- 规格覆盖： 设计文档中的每条需求能否对应到某一任务？漏项则补任务。
- 占位扫描： 对照上一节，搜
TODO、适当、类似等红线词并修正。 - 命名一致： 后文出现的函数名/类型名是否与前面任务一致。
计划审查子代理（可选）
若计划规模大或风险高，可在保存前派发审查子代理，模板见 references/plan-document-reviewer-prompt.md。
交付与执行交接
保存计划后，向用户说明执行方式并二选一（或用户指定）：
- 子代理驱动（推荐）： 每任务新子代理，任务间做规格符合性审查 → 代码质量审查。调用
subagent-driven-development（子代理驱动开发）。 - 同会话逐步执行： 由当前对话按勾选执行，每完成若干任务或与用户约定节点做一次同步；实施时遵循
tdd-master（TDD 开发大师）的红绿重构；关键节点用code-review-expert（代码审查专家）做质量门禁。
禁止在未获用户同意时在 main/master 上直接开始实施（若计划针对默认分支，须在计划中或交接时明确分支策略）。
衔接关系
| 技能 | 关系 |
|---|---|
brainstorming（方案设计师） | 本技能的上游：输入为已批准的设计文档 |
subagent-driven-development（子代理驱动开发） | 本技能的推荐执行方式 |
tdd-master（TDD 开发大师） | 子代理或本会话实施时的测试节奏依据 |
code-review-expert（代码审查专家） | 全量收尾或子代理流程中的质量审查依据 |
prd-engineer（需求工程师） | 偏 PRD/问题域；本技能偏工程切片与文件级步骤，二者可衔接但职责不同 |
© ProgrammerAnthony, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in skills/writing-plans of ProgrammerAnthony/Expert-Coding-Harness.
- SKILL.md
- references/plan-document-reviewer-prompt.md
- references/plan-template.md
Open the folder on GitHubat commit ab0b827
Compare with similar skills
Writing Plans next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Writing Plans this skillProgrammerAnthony/Expert-Coding-Harness | 235 | — | ~876 | Automated safety check: Pass | MIT | |
| Deep Planpiercelamb/deep-plan | 101 | — | ~4.8k | Automated safety check: Pass | MIT | |
| Plan Py4vaspvasp-dev/py4vasp | 100 | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Test-First Implementation Plangittower/git-flow-next | 458 | — | ~1.3k | Automated safety check: Notes | Custom licence | |
| Solo BuildLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.6k | Automated safety check: Notes | MIT | |
| Executing Plansdev-toolings/superpowers-symfony | 222 | — | ~405 | Automated safety check: Notes | MIT |
Similar skills
Plan Py4vasp
vasp-dev/py4vasp
Plan a py4vasp change as an ordered list of test-first chunks — that chunk list is the plan.
Test-First Implementation Plan
gittower/git-flow-next
Builds a two-phase implementation plan from a spec issue, analysis or concept, writing a detailed test plan first and the implementation outline second.
Solo Build
LeoYeAI/openclaw-master-skills
Execute implementation plan tasks with TDD workflow, auto-commit, and phase gates.
Executing Plans
dev-toolings/superpowers-symfony
Methodically execute implementation plans with a TDD approach, incremental commits, and continuous validation
Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
More from ProgrammerAnthony/Expert-Coding-Harness
All 23 skills in this repoArchitecture Advisor
ProgrammerAnthony/Expert-Coding-Harness
A skill your agent uses when 用户需要设计新系统架构、评审或优化已有系统架构、选择技术方案时。触发场景：架构分析、架构设计、系统设计、architecture、架构优化、系统架构、架构评审、架构咨询、技术方案、技术设计、如何组织代码结构、模块划分、服务拆分、数据库选型、微服务设计。
Code Review Expert
ProgrammerAnthony/Expert-Coding-Harness
A skill your agent uses when 用户要求审查代码、评估代码质量、提交 PR 前检查、发现代码有潜在问题时。触发场景：代码审查、code review、审查代码、review、检查代码、代码检查、代码质量、代码评审、这段代码有问题吗、帮我看看代码、合并前检查。
Code Security Audit
ProgrammerAnthony/Expert-Coding-Harness
A skill your agent uses when 用户需要对代码进行安全审计、发现安全漏洞、上线前安全评估、检查代码是否存在安全风险时。触发场景：代码安全审计、安全审计、白盒审计、安全扫描、漏洞检测、漏洞挖掘、SQL注入、命令注入、XSS、SSRF、反序列化、认证绕过、越权、代码安全检查、security audit、code…
Debug Expert
ProgrammerAnthony/Expert-Coding-Harness
A skill your agent uses when 程序出现错误、异常、崩溃，或行为与预期不符，或测试失败，或无法定位问题根因时。触发场景：调试、debug、报错、错误、异常、bug、问题排查、故障排查、不工作、崩溃、无法运行、出错了、为什么不生效、运行报错、跑不起来、程序挂了。
Frontend Code Review
ProgrammerAnthony/Expert-Coding-Harness
A skill your agent uses when 用户需要审查前端代码（React/Vue/Next.js/TypeScript/Tailwind等）、检查代码质量、性能问题、可维护性、安全漏洞、最佳实践落地时。触发场景：前端代码评审、前端代码优化、React/Vue代码检查、TypeScript代码审查、前端性能优化、前端安全审计、前端代码规范检查。
Frontend Performance Optimization
ProgrammerAnthony/Expert-Coding-Harness
A skill your agent uses when 用户需要优化前端性能、提升页面加载速度、减少白屏时间、优化交互流畅度、进行性能排查时。触发场景：前端性能优化、页面加载慢、白屏时间长、卡顿、LCP/FID/CLS指标优化、前端性能分析、打包体积优化。
Related
Categories
Questions about Writing Plans
What does Writing Plans do?
A skill your agent uses when 已有经批准的设计/规格说明、多步骤实施任务，在动代码之前需要可执行任务清单时。触发场景：写实施计划、拆解开发任务、implementation plan、执行计划文档、任务拆分、按 TDD 步骤写计划。. Writing Plans is an agent skill from ProgrammerAnthony/Expert-Coding-Harness.
When should I use Writing Plans?
Writing Plans fits situations like: 已有经批准的设计/规格说明、多步骤实施任务，在动代码之前需要可执行任务清单时。触发场景：写实施计划、拆解开发任务、implementation plan、执行计划文档、任务拆分、按 TDD 步骤写计划; tasks that involve Planning; tasks that involve Test-driven development.
How do I install Writing Plans in Claude Code?
Run `npx skills add ProgrammerAnthony/Expert-Coding-Harness --skill writing-plans -a claude-code`. Or copy the skill folder (skills/writing-plans in ProgrammerAnthony/Expert-Coding-Harness) into .claude/skills/writing-plans in your project. Claude Code loads it when a task matches its description.
How do I install Writing Plans in Codex?
Run `npx skills add ProgrammerAnthony/Expert-Coding-Harness --skill writing-plans -a codex`. Or copy the skill folder (skills/writing-plans in ProgrammerAnthony/Expert-Coding-Harness) into .agents/skills/writing-plans in your project. Codex loads it when a task matches its description.
Can I use Writing Plans in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ProgrammerAnthony/Expert-Coding-Harness --skill writing-plans -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing-plans, .gemini/skills/writing-plans, .github/skills/writing-plans and .opencode/skills/writing-plans in your project.
What does Writing Plans need to run?
Going by SKILL.md and its folder, Writing Plans needs the command-line tools its instructions call (npm, go and cargo). Our summary lists: Python 3.
Does Writing Plans access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Writing Plans safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Writing Plans use?
Writing Plans is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Writing Plans use?
About 876 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 788 tokens, read only when the agent opens those files.
What are the alternatives to Writing Plans?
Skills that share tags, products or a category with Writing Plans: Deep Plan (piercelamb/deep-plan, 101 stars), Plan Py4vasp (vasp-dev/py4vasp, 100 stars), Test-First Implementation Plan (gittower/git-flow-next, 458 stars) and Solo Build (LeoYeAI/openclaw-master-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Writing Plans?
ProgrammerAnthony (a GitHub user) maintains it in ProgrammerAnthony/Expert-Coding-Harness, which has 235 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on May 11, 2026.
Source: ProgrammerAnthony/Expert-Coding-Harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.