MicrosoftKnown publishermicrosoft-foundry/foundry-agent-webapp/.github/skills/planning-features/SKILL.mdplanning-features
Skill124 starsChanged 7 months agoMITView on GitHub
Provides structured plan template for feature implementation. Use when planning new features, multi-file changes, or creating implementation roadmaps before coding.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- juanitourquiza/shipframetheir own version, first seen Oct 23, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- juanitourquiza/shipframe★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- committing-codeSkill
- deploying-to-azureSkill
- implementing-chat-streamingSkill
- researching-azure-ai-sdkSkill
- reviewing-documentationSkill
- syncing-mcp-serversSkill
- testing-cli-compatibilitySkill
- testing-with-playwrightSkill
- triaging-issuesSkill
- troubleshooting-authenticationSkill
- understanding-architectureSkill
- validating-deploymentsSkill
- validating-local-setupSkill
- validating-ui-featuresSkill
- writing-bicep-templatesSkill
- writing-csharp-codeSkill
- writing-typescript-codeSkill
- writing-unit-tests-csharpSkill
- writing-unit-tests-typescriptSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Search existing patterns before proposing new ones — reuse what the codebase already does
- Very specific: line 23
Read relevant skills (e.g., writing-csharp-code, writing-typescript-code, writing-bicep-templates) to follow project conventions
- Distinctive: line 24
Check current implementations in files you plan to modify so the plan reflects actual code structure
- Distinctive: line 28
Every plan must include these sections:
- Distinctive: line 69
Document each edge case and how the implementation should handle it.
- Very specific: line 72
If the plan affects state machines, SSE events, or API endpoints, include updates to ARCHITECTURE-FLOW.md.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.