ワンクリックでManusで任意のスキルを実行

始める

deep-plan

スター1

フォーク0

更新日2026年2月10日 21:35

Create thorough implementation plans for complex tasks.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

win20

win20/dotfiles

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Deep Plan

Overview

Produce a detailed, actionable implementation plan, then save it into the project at .agent.local/plans/ using a date-prefixed filename or a phased folder structure.

Workflow

Gather context
- Read relevant files to understand existing structure, conventions, and dependencies.
- Note any constraints (tech stack, lint rules, coding conventions).
Clarify missing requirements
- If anything is ambiguous or risky, ask concise clarifying questions before planning.
Generate the plan
- If subagent support is available: Spawn a subagent with instructions from ./references/guidelines.md
- Otherwise: Apply the guidelines from ./references/guidelines.md directly to create the plan yourself
- The guidelines specify the required format, process, and best practices
Save the plan
- Write to .agent.local/plans/<DD-MM-YYYY>-<feature-slug>.md
- If the plan contains multiple big phases, create .agent.local/plans/<DD-MM-YYYY>-<feature-slug>/phase-1.md, phase-2.md, etc.

Naming Rules

Use date prefix in DD-MM-YYYY format
Use a short, lowercase, hyphenated feature slug (e.g., 03-02-2026-profile-onboarding.md)
Keep file names ASCII

このリポジトリの他の Skills

同じリポジトリ

git-commit

win20/dotfiles

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use whenever commiting changes to git.

2026-02-271

local-review

win20/dotfiles

Code reviews of git changes without creating actual PR.

2026-02-261

create-changelog

win20/dotfiles

Creates non-technical changelogs from git commits.

2026-02-041

create-prompt

win20/dotfiles

Rewrite user requests into clear, precise, and complete AI prompts. Use when a user asks to create, convert, or refine a prompt, or to restate a request as a specification for an AI model.

2026-02-041

documentation

win20/dotfiles

Create clear, concise technical documentation for a specified file, module, or folder.

2026-02-041

pr-summary

win20/dotfiles

Generate pull request summaries and open GitHub PRs from the current branch’s git changes.

2026-02-041

name	deep-plan
description	Create thorough implementation plans for complex tasks.

Deep Plan

Overview

Produce a detailed, actionable implementation plan, then save it into the project at .agent.local/plans/ using a date-prefixed filename or a phased folder structure.

Workflow

Gather context
- Read relevant files to understand existing structure, conventions, and dependencies.
- Note any constraints (tech stack, lint rules, coding conventions).
Clarify missing requirements
- If anything is ambiguous or risky, ask concise clarifying questions before planning.
Generate the plan
- If subagent support is available: Spawn a subagent with instructions from ./references/guidelines.md
- Otherwise: Apply the guidelines from ./references/guidelines.md directly to create the plan yourself
- The guidelines specify the required format, process, and best practices
Save the plan
- Write to .agent.local/plans/<DD-MM-YYYY>-<feature-slug>.md
- If the plan contains multiple big phases, create .agent.local/plans/<DD-MM-YYYY>-<feature-slug>/phase-1.md, phase-2.md, etc.

Naming Rules

Use date prefix in DD-MM-YYYY format
Use a short, lowercase, hyphenated feature slug (e.g., 03-02-2026-profile-onboarding.md)
Keep file names ASCII