# writing-plans

> Use when you have a spec or requirements for a multi-step task, before touching code

- Author: lijt
- Repository: kofttlcc/stls
- Version: 20260206163149
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-06
- Source: https://github.com/kofttlcc/stls
- Web: https://mule.run/skillshub/@@kofttlcc/stls~writing-plans:20260206163149

---

---
name: writing-plans
description: >-
  Use when you have a spec or requirements for a multi-step task, before
  touching code
trigger: when_needed
language: zh-TW
adapted_from: openskills/writing-plans
version: 1.0.0-antigravity
original_license: Unknown
---
# WRITING-PLANS 處理指南

> **技能版本**: v1.0 (Antigravity 適配版)  
> **原始來源**: openskills/writing-plans  
> **語言**: 繁體中文

## 概述

Use when you have a spec or requirements for a multi-step task, before touching code

---


# Writing Plans

## 使用情境

此技能適用於以下情況：
- 用戶明確要求相關功能時
- 任務需要專業領域知識時
- 需要遵循特定工作流程時

---

## 概述

Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.

Assume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.

**Announce at start:** "I'm using the writing-plans skill to create the implementation plan."

**Context:** This should be run in a dedicated worktree (created by brainstorming skill).

**Save plans to:** `docs/plans/YYYY-MM-DD-<feature-name>.md`

## Bite-Sized Task Granularity

**Each step is one action (2-5 minutes):**
- "Write the failing test" - step
- "Run it to make sure it fails" - step
- "Implement the minimal code to make the test pass" - step
- "Run the tests and make sure they pass" - step
- "Commit" - step

## Plan Document Header

**Every plan MUST start with this header:**


詳細內容請參閱：[example_3.txt](examples/example_3.txt)


## Task Structure


詳細內容請參閱：[example_4.txt](examples/example_4.txt)


**Step 2: Run test to verify it fails**

Run: `pytest tests/path/test.py::test_name -v`
Expected: FAIL with "function not defined"

**Step 3: Write minimal implementation**

```python
def function(input):
    return expected

詳細內容請參閱：[example_5.txt](examples/example_5.txt)

```

## Remember
- Exact file paths always
- Complete code in plan (not "add validation")
- Exact commands with expected output
- Reference relevant skills with @ syntax
- DRY, YAGNI, TDD, frequent commits

## Execution Handoff

After saving the plan, offer execution choice:

**"Plan complete and saved to `docs/plans/<filename>.md`. Two execution options:**

**1. Subagent-Driven (this session)** - I dispatch fresh subagent per task, review between tasks, fast iteration

**2. Parallel Session (separate)** - Open new session with executing-plans, batch execution with checkpoints

**Which approach?"**

**If Subagent-Driven chosen:**
- **REQUIRED SUB-SKILL:** Use superpowers:subagent-driven-development
- Stay in this session
- Fresh subagent per task + code review

**If Parallel Session chosen:**
- Guide them to open new session in worktree
- **REQUIRED SUB-SKILL:** New session uses superpowers:executing-plans


---

## 專案整合

此技能已適配 Antigravity 系統：

- 遵循 `skills/_base/coding_style.md` 編碼規範
- 與 `skills/_base/architecture.md` 架構模式一致
- 符合 Constitution v3.1 語言規範 (繁體中文)

### 相關技能

可搭配以下技能使用：
- `systematic-debugging` - 系統化除錯
- `verification-before-completion` - 完成前驗證