plan

Sterne6

Forks0

Aktualisiert23. Juli 2026 um 16:35

Use when the user asks for an implementation plan for a package, feature, migration, or refactor. Research the relevant code and produce one concrete, execution-ready plan.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

phcurado

phcurado/dotfiles

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	plan
description	Use when the user asks for an implementation plan for a package, feature, migration, or refactor. Research the relevant code and produce one concrete, execution-ready plan.

Plan

Inspect the target implementation, direct consumers, relevant tests, and established local patterns. Research further only when it affects the implementation.
Give one recommended plan promptly. State reasonable assumptions; ask only when an answer would materially change the implementation.
Prefer compact artifacts chosen for the task—wire examples, tables, package trees, API signatures, and flow diagrams—over long prose or a fixed template.
Keep the first iteration narrow and cite exact file paths.

Mehr aus diesem Repository

gleiches Repository

brainstorm

phcurado/dotfiles

Use for open-ended brainstorming, ideation, strategy, or tradeoff analysis. Do not use for implementation plans for code, packages, features, migrations, or refactors; use the plan skill instead.

2026-07-236

structural-search

phcurado/dotfiles

Syntax-aware code search and refactoring with ast-grep. Use for precise structural follow-up after broad discovery, or when the user asks for a specific code shape/codemod such as function calls, imports, hooks, JSX, Lua API calls, or API migrations. Do not use as the first pass for broad inventories, plain text, docs, configs, logs, or fuzzy discovery.

2026-06-196

grill-me

phcurado/dotfiles

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

2026-06-166

name	plan
description	Use when the user asks for an implementation plan for a package, feature, migration, or refactor. Research the relevant code and produce one concrete, execution-ready plan.

Plan

Inspect the target implementation, direct consumers, relevant tests, and established local patterns. Research further only when it affects the implementation.
Give one recommended plan promptly. State reasonable assumptions; ask only when an answer would materially change the implementation.
Prefer compact artifacts chosen for the task—wire examples, tables, package trees, API signatures, and flow diagrams—over long prose or a fixed template.
Keep the first iteration narrow and cite exact file paths.