Menu
Use when the user asks to plan a Navigator feature, write an implementation plan, create or update an ExecPlan, break down a substantial change into milestones, or prepare a self-contained specification before coding.
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ê.
Use when creating, modifying, testing, packaging, or documenting Navigator.Extensions.* packages, extension options, extension services, pipeline steps, action builder methods, extension samples, or extension-specific README examples.
Use when working inside the Navigator repository to create, modify, or validate .NET projects, solution structure, tests, samples, extensions, or strategies. This skill defines the required `dotnet` CLI workflow, naming conventions, project placement, and validation commands for this solution.
Use when working on Navigator core behavior, request processing, dependency injection, action resolution, execution pipelines, argument resolution, tracing, webhook handling, or any change that needs understanding of the framework runtime architecture.
Baseado na classificação ocupacional SOC
| name | navigator-execplan |
| description | Use when the user asks to plan a Navigator feature, write an implementation plan, create or update an ExecPlan, break down a substantial change into milestones, or prepare a self-contained specification before coding. |
Use this skill when the user asks for a plan for a feature or substantial repository change.
Read .agents/PLANS.md before writing, updating, or implementing an ExecPlan. That file is the source of truth for the required structure, tone, self-contained context, progress tracking, validation, and living-document rules.
If the plan involves core runtime behavior, also use navigator-architecture and read docs/ARCHITECTURE.md.
If the plan involves Navigator.Extensions.*, also use navigator-extension-authoring and read docs/EXTENSION-AUTHORING.md.
If the plan involves project or solution layout, also use navigator-solution.
ProgressSurprises & DiscoveriesDecision LogOutcomes & Retrospective.agents/PLANS.md exactly.md code block.Progress.Plans for code changes should end with strict validation from src/ unless there is a documented reason not to:
dotnet restore
dotnet build -c Release --no-restore
dotnet test -c Release --no-build --verbosity normal
For documentation-only plans, specify a concrete review or consistency check instead of pretending a build proves the doc change.