Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

Começar

create-plan

Estrelas340

Forks34

Atualizado22 de fevereiro de 2026 às 23:13

Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

Kxiandaoyan

Kxiandaoyan/Memoh-v2

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	create-plan
description	Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.

Create Plan

Goal

Turn a user prompt into a single, actionable plan delivered in the final assistant message.

Minimal Workflow

Throughout the entire workflow, operate in read-only mode. Do not write or update files.

Scan context quickly
- Read README.md and any obvious docs (docs/, CONTRIBUTING.md, ARCHITECTURE.md).
- Skim relevant files (the ones most likely touched).
- Identify constraints (language, frameworks, CI/test commands, deployment shape).
Ask follow-ups only if blocking
- Ask at most 1–2 questions.
- Only ask if you cannot responsibly plan without the answer; prefer multiple-choice.
- If unsure but not blocked, make a reasonable assumption and proceed.
Create a plan using the template below
- Start with 1 short paragraph describing the intent and approach.
- Clearly call out what is in scope and what is not in scope in short.
- Then provide a small checklist of action items (default 6–10 items).
  - Each checklist item should be a concrete action and, when helpful, mention files/commands.
  - Make items atomic and ordered: discovery → changes → tests → rollout.
  - Verb-first: "Add…", "Refactor…", "Verify…", "Ship…".
- Include at least one item for tests/validation and one for edge cases/risk when applicable.
- If there are unknowns, include a tiny Open questions section (max 3).
Do not preface the plan with meta explanations; output only the plan as per template

Plan Template (Follow Exactly)

# Plan

<1–3 sentences: what we're doing, why, and the high-level approach.>

## Scope
- In:
- Out:

## Action items
[ ] <Step 1>
[ ] <Step 2>
[ ] <Step 3>
[ ] <Step 4>
[ ] <Step 5>
[ ] <Step 6>

## Open questions
- <Question 1>
- <Question 2>
- <Question 3>

Checklist Item Guidance

Good checklist items:

Point to likely files/modules: src/..., app/..., services/...
Name concrete validation: "Run npm test", "Add unit tests for X"
Include safe rollout when relevant: feature flag, migration plan, rollback note

Avoid:

Vague steps ("handle backend", "do auth")
Too many micro-steps
Writing code snippets (keep the plan implementation-agnostic)

Mais deste repositório

mesmo repositório

docx

Kxiandaoyan/Memoh-v2

Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks

2026-02-26340

pdf

Kxiandaoyan/Memoh-v2

Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.

2026-02-26340

pptx

Kxiandaoyan/Memoh-v2

Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks

2026-02-26340

xlsx

Kxiandaoyan/Memoh-v2

Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv, etc) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing data, (3) Modify existing spreadsheets while preserving formulas, (4) Data analysis and visualization in spreadsheets, or (5) Recalculating formulas

2026-02-26340

agent-reach

Kxiandaoyan/Memoh-v2

Give your AI Agent eyes to see the entire internet. Search + read 10+ platforms with one install.

2026-02-24340

frontend-slides

Kxiandaoyan/Memoh-v2

Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.

2026-02-24340

Create Plan

Goal

Turn a user prompt into a single, actionable plan delivered in the final assistant message.

Minimal Workflow

Throughout the entire workflow, operate in read-only mode. Do not write or update files.

Scan context quickly

Read README.md and any obvious docs (docs/, CONTRIBUTING.md, ARCHITECTURE.md).
Skim relevant files (the ones most likely touched).
Identify constraints (language, frameworks, CI/test commands, deployment shape).

Ask follow-ups only if blocking

Ask at most 1–2 questions.
Only ask if you cannot responsibly plan without the answer; prefer multiple-choice.
If unsure but not blocked, make a reasonable assumption and proceed.

Create a plan using the template below

Start with 1 short paragraph describing the intent and approach.
Clearly call out what is in scope and what is not in scope in short.
Then provide a small checklist of action items (default 6–10 items).
- Each checklist item should be a concrete action and, when helpful, mention files/commands.
- Make items atomic and ordered: discovery → changes → tests → rollout.
- Verb-first: "Add…", "Refactor…", "Verify…", "Ship…".
Include at least one item for tests/validation and one for edge cases/risk when applicable.
If there are unknowns, include a tiny Open questions section (max 3).

Do not preface the plan with meta explanations; output only the plan as per template

Plan Template (Follow Exactly)

# Plan <1–3 sentences: what we're doing, why, and the high-level approach.> ## Scope - In: - Out: ## Action items [ ] <Step 1> [ ] <Step 2> [ ] <Step 3> [ ] <Step 4> [ ] <Step 5> [ ] <Step 6> ## Open questions - <Question 1> - <Question 2> - <Question 3>

Checklist Item Guidance

Good checklist items:

Point to likely files/modules: src/..., app/..., services/...

Name concrete validation: "Run npm test", "Add unit tests for X"

Include safe rollout when relevant: feature flag, migration plan, rollback note

Avoid:

Vague steps ("handle backend", "do auth")

Too many micro-steps

Writing code snippets (keep the plan implementation-agnostic)