一键在 Manus 中运行任何 Skill

开始使用

plan-write

星标2

分支0

更新时间2026年7月5日 18:11

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

安装

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

在 Manus 中运行

来源

SyahrulBhudiF

SyahrulBhudiF/dotfiles

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

下载

在 Manus 中运行

Writing Plans: Implementation Blueprint

1. Overview & Setup

Purpose: Create a zero-context, multi-step implementation plan for a developer.
Storage: Always save to docs/plans/YYYY-MM-DD-<feature-name>.md.
Announce: "I'm using the writing-plans skill to create the implementation plan."
Context: Assume the developer is skilled but knows nothing of the codebase, domain, or good test design.

2. Core Principles

TDD Lifecycle: Failing test -> Verify fail -> Minimal code -> Verify pass -> Commit.
Granularity: Each task should take 2–5 minutes.
DRY/YAGNI: Keep it lean; no unnecessary abstractions.
Reference: Use @ syntax for relevant skills/docs.

3. Required Plan Header

# [Feature Name] Implementation Plan

> **IMPORTANT**: Use plan-execute skill to implement this plan task-by-task.

**Goal:** [One sentence goal]
**Architecture:** [2-3 sentences on approach]
**Tech Stack:** [Key libraries/tools]

---

同仓库更多 Skills

同仓库

code-review-git

SyahrulBhudiF/dotfiles

Code review using Git

2026-07-052

code-review-jj

SyahrulBhudiF/dotfiles

Code review using Jujutsu

2026-07-052

plan-design

SyahrulBhudiF/dotfiles

Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes

2026-07-052

plan-execute

SyahrulBhudiF/dotfiles

Use when you have a written implementation plan to execute in a separate session with review checkpoints

2026-07-052

prd

SyahrulBhudiF/dotfiles

Convert plan to actionable structured PRDs

2026-07-052

caveman-distilate

SyahrulBhudiF/dotfiles

Ultra-compressed communication mode. Distills AI output to its core — ~65% fewer tokens while keeping full technical accuracy. Use when user says "caveman", "terse", "kurz", "kurz&knapp", "kurz bitte", "less tokens", "weniger text", or invokes /caveman-distillate.

2026-05-042

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

Writing Plans: Implementation Blueprint

1. Overview & Setup

Purpose: Create a zero-context, multi-step implementation plan for a developer.
Storage: Always save to docs/plans/YYYY-MM-DD-<feature-name>.md.
Announce: "I'm using the writing-plans skill to create the implementation plan."
Context: Assume the developer is skilled but knows nothing of the codebase, domain, or good test design.

2. Core Principles

TDD Lifecycle: Failing test -> Verify fail -> Minimal code -> Verify pass -> Commit.
Granularity: Each task should take 2–5 minutes.
DRY/YAGNI: Keep it lean; no unnecessary abstractions.
Reference: Use @ syntax for relevant skills/docs.

3. Required Plan Header

# [Feature Name] Implementation Plan

> **IMPORTANT**: Use plan-execute skill to implement this plan task-by-task.

**Goal:** [One sentence goal]
**Architecture:** [2-3 sentences on approach]
**Tech Stack:** [Key libraries/tools]

---