planning Skill
Plan broad or risky Nacelle work. Use for architecture changes, migrations, release or production-readiness assessments, security hardening, performance baselines, documentation restructuring, validation strategies, or multi-session work. Published by microsoft in nacelle.
Decision snapshot
Is this a fit?
Security review, Documentation, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is planning Skill?
Plan broad or risky Nacelle work. Use for architecture changes, migrations, release or production-readiness assessments, security hardening, performance baselines, documentation restructuring, validation strategies, or multi-session work. Published by microsoft in nacelle. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Security review
- Documentation
- Security review use cases
- Documentation use cases
Declared skill metadata
- Source file: .github/skills/planning/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use planning Skill
- Use it for security review.
- Use it for documentation.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/nacelle
- Skill file: .github/skills/planning/SKILL.md
What it does
Plan broad or risky Nacelle work. Use for architecture changes, migrations, release or production-readiness assessments, security hardening, performance baselines, documentation restructuring, validation strategies, or multi-session work.
Skill instructions
Planning Nacelle Work Turn substantial goals into scoped, ordered work with explicit risks, validation gates, and handoff-ready checkpoints. Scope - Inspect the relevant repository state, architecture documentation, manifests, modules, tests, configuration, scripts, CI, and recent commits before planning. - Use chat for narrow plans. Create or update a durable plan for broad, risky, architectural, release, migration, or multi-session work when the user requests one or the work needs a persistent handoff. - Continue the nearest existing plan when it matches the goal. If no convention exists and a durable plan is justified, use .github/plans/YYYY-MM-DD-<topic.md. - Keep internal assessments and decisions separate from public operator, API, user, and release documentation. - Leave implementation tactics to the owning crate and nearby code unless they affect ordering, risk, validation, compatibility, or architecture. - When the user requests only a plan, do not implement or commit changes.
Verified compatibility and discovery
Frequently asked questions
What is planning?
planning is a open-source AI agent skill with Copy skill directory. Plan broad or risky Nacelle work. Use for architecture changes, migrations, release or production-readiness assessments, security hardening, performance baselines, documentation restructuring, validation.
Who is planning best for?
planning is best for reusing agent instructions, scripts, and references, security review workflows, documentation workflows.
How do I install planning?
Install or run planning using Copy skill directory. Check planning for the latest setup command.
Is planning actively maintained?
planning may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
