Skip to content
Back to skills

Sp Writing Plans

ASecurity

將明確需求拆成有依賴與驗收條件的多步驟計畫;用於跨檔案或跨階段實作。

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
tools

Works with

  • terminal

Security analysis

A100/100

Scanned September 27, 2026

npx -y skills add ddmanyes/agent-skills-toolkit-zh-tw --skill sp-writing-plans --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Sp Writing Plans?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Sp Writing Plans
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ddmanyes-sp-writing-plans/badge)](https://www.skillsdirectory.com/skills/ddmanyes-sp-writing-plans)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: sp-writing-plans
description: 將明確需求拆成有依賴與驗收條件的多步驟計畫;用於跨檔案或跨階段實作。
allowed-tools: Terminal, Read, Write, Edit, Glob, Grep
---
# 撰寫實作計畫
沿用使用者指定的計畫或專案現有位置;沒有慣例時使用 IMPLEMENTATION_PLAN.md。

計畫至少寫明目標、範圍、必要的檔案/模組、步驟依賴、預期行為與驗證方法。依可獨立驗收的成果分步,不固定每步分鐘數或每步提交。

- 先讀與本次決策直接相關的入口及規範;只有跨模組設計需要時才建立結構圖。
- 未確定的事項寫成有影響與解決方式的待確認項,不用沒有行動意義的佔位符,也不假稱所有細節已知。
- 使用者要求 test-first,或已批准 TDD 時,採每個行為一個 red → green → 必要的 refactor 切片。其他工作選用與風險相稱的現有檢查。
- 每項指明何時算完成及失敗後怎麼處理;在已授權範圍內修復並重跑受影響檢查。
- Commit/push 依原始授權及專案慣例安排,不用計畫自行擴張發布權限。

需要計畫審查時提交具體方案並等待;使用者已批准執行時接續完成工作。以繁體中文說明計畫與未決事項。

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…