一键在 Manus 中运行任何 Skill

plan

星标0

分支0

更新时间2026年2月10日 02:16

Breaks down feature requests into sequential, implementable tasks with code changes under 50 lines each. Use when planning new features, refactors, or multi-step changes to ensure logical ordering and no broken intermediate states.

安装

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

在 Manus 中运行

来源

iulspop

iulspop/mandarin-anki-deck-builder

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

下载

在 Manus 中运行

Implementation Plan

Act as a top-tier software architect specializing in full-stack web development. Break down the following request into manageable, sequential tasks that can be executed one at a time.

Request: $ARGUMENTS

Rules

Follow the project's CLAUDE.md guidelines for all code suggestions.
Observe and conform to existing code style, patterns, and conventions.
Thoroughly search for and read ALL relevant code for the task before making changes.
If necessary, ask the user to gather any additional context or clarification needed BEFORE writing the plan.
If necessary, search the web to look up the latest APIs.
If blocked or uncertain, ask clarifying questions rather than making assumptions.
Break down the plan into distinct tasks.
If a task reveals new information that changes the plan, pause and re-plan.

Task Rules

Tasks should be mostly code changes.
Briefly state the task as a short title.
Tasks should be enumerated.
Only include explanatory text if ABSOLUTELY NECESSARY.
Each task MUST contain the suggested code changes necessary to implement it.
Each task MUST have code changes LESS than 50 lines.
Tasks should come in logical order so they can be implemented one after the other WITHOUT breaking the code.

Write the plan into ai/plans/ with filename format: yyyy-mm-dd-title.md

同仓库更多 Skills

同仓库

better-writer

iulspop/mandarin-anki-deck-builder

Rewrites text to be clearer, simpler, and more engaging using Scott Adams' writing principles and persuasive techniques. Use when editing marketing copy, blog posts, emails, or any business text that needs to be punchier.

2026-02-100

brainstorm

iulspop/mandarin-anki-deck-builder

Facilitates solution ideation with clear trade-offs and a final recommendation. Use when exploring architectural decisions, evaluating technology choices, or comparing implementation approaches before writing code.

2026-02-100

commit

iulspop/mandarin-anki-deck-builder

Commits staged changes using the conventional commits format with proper type, scope, and description. Use when committing code changes to maintain a clean, standardized git history.

2026-02-100

debug

iulspop/mandarin-anki-deck-builder

Structured debugging skill for methodical root cause analysis. Use when investigating bugs, unexpected behavior, or errors. Produces an issue summary, key findings, root cause analysis, and recommended solutions without modifying code.

2026-02-100

documentation

iulspop/mandarin-anki-deck-builder

Generates clear, example-driven documentation with runnable code samples and progressive complexity. Use when writing API docs, guides, READMEs, or any technical documentation.

2026-02-100

log

iulspop/mandarin-anki-deck-builder

Logs completed epics and significant accomplishments in reverse chronological order. Use after completing major features, releases, or architecture changes to maintain a project changelog.

2026-02-100

name	plan
description	Breaks down feature requests into sequential, implementable tasks with code changes under 50 lines each. Use when planning new features, refactors, or multi-step changes to ensure logical ordering and no broken intermediate states.

Implementation Plan

Act as a top-tier software architect specializing in full-stack web development. Break down the following request into manageable, sequential tasks that can be executed one at a time.

Request: $ARGUMENTS

Rules

Follow the project's CLAUDE.md guidelines for all code suggestions.
Observe and conform to existing code style, patterns, and conventions.
Thoroughly search for and read ALL relevant code for the task before making changes.
If necessary, ask the user to gather any additional context or clarification needed BEFORE writing the plan.
If necessary, search the web to look up the latest APIs.
If blocked or uncertain, ask clarifying questions rather than making assumptions.
Break down the plan into distinct tasks.
If a task reveals new information that changes the plan, pause and re-plan.

Task Rules

Tasks should be mostly code changes.
Briefly state the task as a short title.
Tasks should be enumerated.
Only include explanatory text if ABSOLUTELY NECESSARY.
Each task MUST contain the suggested code changes necessary to implement it.
Each task MUST have code changes LESS than 50 lines.
Tasks should come in logical order so they can be implemented one after the other WITHOUT breaking the code.

Write the plan into ai/plans/ with filename format: yyyy-mm-dd-title.md