Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

Comenzar

$pwd:

create-plan

Name: Create Plan
Author: Kxiandaoyan

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

Ejecutar en Manus

$ git log --oneline --stat

stars:342

forks:34

updated:22 de febrero de 2026, 23:13

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)

related-skills.json

mismo repositorio

docx.md

from "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-26342

pdf.md

from "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-26342

pptx.md

from "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-26342

xlsx.md

from "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-26342

agent-reach.md

from "Kxiandaoyan/Memoh-v2"

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

2026-02-24342

imap-smtp-email.md

from "Kxiandaoyan/Memoh-v2"

Read and send email via IMAP/SMTP. Check for new/unread messages, fetch content, search mailboxes, mark as read/unread, and send emails with attachments. Works with any IMAP/SMTP server including Gmail, Outlook, 163.com, vip.163.com, 126.com, vip.126.com, 188.com, and vip.188.com.

2026-02-22342

package.json

"author": "Kxiandaoyan"

"repository": "Kxiandaoyan/Memoh-v2"

Abrir repositorio de GitHub Ver repositorios del creador

$ install --global

$ download --local

Ejecutar en Manus

$ useful --forSOC

Otras ocupaciones informáticasOcupaciones informáticas y matemáticas15-1299L4

Desarrolladores de softwareL4

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)

create-plan

Create Plan

Goal

Minimal Workflow

Plan Template (Follow Exactly)

Checklist Item Guidance

Más de este repositorio

Más de este repositorio

Create Plan

Goal

Minimal Workflow

Plan Template (Follow Exactly)

Checklist Item Guidance