MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
Provides structured plan template for feature implementation.
Install Planning Features
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill planning-features -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp planning-features --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/planning-features .claude/skills/planning-features && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "planning-features" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/planning-features into .claude/skills/planning-features/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-features", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/planning-featuresType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill planning-features -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp planning-features --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/planning-features .agents/skills/planning-features && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "planning-features" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/planning-features into .agents/skills/planning-features/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-features", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill planning-features -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp planning-features --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/planning-features .cursor/skills/planning-features && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "planning-features" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/planning-features into .cursor/skills/planning-features/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-features", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/microsoft-foundry/foundry-agent-webapp.git --path .github/skills/planning-features--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill planning-features -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp planning-features --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/planning-features .gemini/skills/planning-features && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "planning-features" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/planning-features into .gemini/skills/planning-features/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-features", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install microsoft-foundry/foundry-agent-webapp planning-featuresInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill planning-features -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/planning-features .github/skills/planning-features && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "planning-features" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/planning-features into .github/skills/planning-features/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-features", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add microsoft-foundry/foundry-agent-webapp --skill planning-features -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install microsoft-foundry/foundry-agent-webapp planning-features --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/microsoft-foundry/foundry-agent-webapp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/planning-features .opencode/skills/planning-features && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "planning-features" agent skill from https://github.com/microsoft-foundry/foundry-agent-webapp/tree/main/.github/skills/planning-features into .opencode/skills/planning-features/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-features", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
planning-features- GitHub stars
- 127
- Token cost
- ~548 tokens
- SKILL.md length
- 199 words
- Files
- 1
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- MIT
At a glance
Provides structured plan template for feature implementation.
- Works in 8 steps: Overview → Requirements → Files to Modify → …
- Planning new features
- SKILL.md covers Research-First Workflow and Required Plan Structure
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Planning Features is an agent skill from microsoft-foundry/foundry-agent-webapp. Provides structured plan template for feature implementation. Use when planning new features, multi-file changes, or creating implementation roadmaps before coding.
Its SKILL.md is about 550 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows. The repository describes itself as: GitHub Copilot enabled repo for building and deploying a web application with Entra ID authentication and integrated with Azure AI Foundry Agents. The licence is MIT.
When your agent uses it
- Planning new features
- Multi-file changes
- Creating implementation roadmaps before coding
Example prompts
- “Use the planning-features skill to provide structured plan template for feature implementation”
- “/planning-features”
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit f6cb362. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Planning Features loads about 548 tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 199 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from microsoft-foundry/foundry-agent-webapp at commit f6cb362, republished under its MIT licence (© microsoft-foundry). 199 words, ~548 tokens.
Download SKILL.mdSave it as
.claude/skills/planning-features/SKILL.md (or your agent's skills folder).- name
- planning-features
- description
- Provides structured plan template for feature implementation. Use when planning new features, multi-file changes, or creating implementation roadmaps before coding.
Feature Planning
Tip: For read-only planning mode, press Shift+Tab in VS Code or Copilot CLI to enter built-in plan mode.
Research-First Workflow
- Understand the request — clarify scope and success criteria
- Search the codebase for existing patterns and relevant files
- Load relevant skills from
.github/skills/for project conventions - Generate a structured plan using the template below
Research Guidelines
- Search existing patterns before proposing new ones — reuse what the codebase already does
- Read relevant skills (e.g.,
writing-csharp-code,writing-typescript-code,writing-bicep-templates) to follow project conventions - Check current implementations in files you plan to modify so the plan reflects actual code structure
Required Plan Structure
Every plan must include these sections:
1. Overview
2-3 sentence description of the feature or change.
2. Requirements
- [ ] Requirement one
- [ ] Requirement two3. Files to Modify
| File Path | Changes |
|---|---|
path/to/file | Description of modifications |
4. Files to Create
| File Path | Purpose |
|---|---|
path/to/new/file | What this file does |
5. Implementation Steps
Numbered steps with sub-steps. Reference skill patterns where applicable.
1. Step one
- Sub-step referencing `writing-csharp-code` skill patterns
- Sub-step with specific code location
2. Step two
- Sub-step referencing `writing-typescript-code` skill patterns6. Testing Checklist
- [ ] Manual verification step one
- [ ] Manual verification step two7. Edge Cases
Document each edge case and how the implementation should handle it.
8. Documentation Updates
If the plan affects state machines, SSE events, or API endpoints, include updates to ARCHITECTURE-FLOW.md. Load the understanding-architecture skill for validation rules.
© microsoft-foundry, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .github/skills/planning-features of microsoft-foundry/foundry-agent-webapp.
Open the folder on GitHubat commit f6cb362
Compare with similar skills
Planning Features next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Planning Features this skillmicrosoft-foundry/foundry-agent-webapp | 127 | — | ~548 | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 64 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 11 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 | |
| Using Superpowersfarm-fe/farm | 5.6k | 35 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Executing Plans Inlineobra/superpowers | 296k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Claude Code Agent Developmentanthropics/claude-plugins-official | 38k | 8 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
- Official
Hook Development for Claude Code Plugins
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
Using Superpowers
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
- Official
Claude Code Agent Development
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
- Official
Skill Creator
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
More from microsoft-foundry/foundry-agent-webapp
All 19 skills in this repoCommitting Code
microsoft-foundry/foundry-agent-webapp
Provides commit message format and workflow for this repository.
Implementing Chat Streaming
microsoft-foundry/foundry-agent-webapp
Provides SSE streaming patterns for the chat API and frontend.
Researching Azure AI SDK
microsoft-foundry/foundry-agent-webapp
Provides research patterns for Foundry Agent Service SDK. An agent skill from microsoft-foundry/foundry-agent-webapp.
Deploying To Azure
microsoft-foundry/foundry-agent-webapp
Provides deployment commands and troubleshooting for Azure Container Apps.
Syncing MCP Servers
microsoft-foundry/foundry-agent-webapp
Synchronize MCP server configuration between VS Code (.vscode/mcp.json) and Copilot CLI (~/.copilot/mcp-config.json).
Testing CLI Compatibility
microsoft-foundry/foundry-agent-webapp
Validate that Copilot CLI can see all repo skills, MCP servers, and custom instructions.
Related
Categories
Questions about Planning Features
What does Planning Features do?
Provides structured plan template for feature implementation. Planning Features is an agent skill from microsoft-foundry/foundry-agent-webapp. Provides structured plan template for feature implementation.
When should I use Planning Features?
Planning Features fits situations like: planning new features; multi-file changes; creating implementation roadmaps before coding.
How do I install Planning Features in Claude Code?
Run `npx skills add microsoft-foundry/foundry-agent-webapp --skill planning-features -a claude-code`. Or copy the skill folder (.github/skills/planning-features in microsoft-foundry/foundry-agent-webapp) into .claude/skills/planning-features in your project. Claude Code loads it when a task matches its description.
How do I install Planning Features in Codex?
Run `npx skills add microsoft-foundry/foundry-agent-webapp --skill planning-features -a codex`. Or copy the skill folder (.github/skills/planning-features in microsoft-foundry/foundry-agent-webapp) into .agents/skills/planning-features in your project. Codex loads it when a task matches its description.
Can I use Planning Features in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add microsoft-foundry/foundry-agent-webapp --skill planning-features -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/planning-features, .gemini/skills/planning-features, .github/skills/planning-features and .opencode/skills/planning-features in your project.
What does Planning Features need to run?
SKILL.md names no scripts, command-line tools or credentials: Planning Features is instructions for the agent only.
Does Planning Features access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Planning Features safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Planning Features use?
Planning Features is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Planning Features use?
About 548 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Planning Features?
Skills that share tags, products or a category with Planning Features: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Planning Features?
microsoft-foundry (a GitHub organization) maintains it in microsoft-foundry/foundry-agent-webapp, which has 127 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on April 21, 2026.
Source: microsoft-foundry/foundry-agent-webapp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.