architectural-proposals Skill
How to write comprehensive architectural proposals that drive alignment before code is written Published by microsoft in aitour26-BRK445-building-enterprise-ready-ai-agents-with-microsoft-foundry.
Decision snapshot
Is this a fit?
Documentation, Writing, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
5 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is architectural-proposals Skill?
How to write comprehensive architectural proposals that drive alignment before code is written Published by microsoft in aitour26-BRK445-building-enterprise-ready-ai-agents-with-microsoft-foundry. 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
- Documentation
- Writing
- Documentation use cases
- Writing use cases
Declared skill metadata
- Source file: .copilot/skills/architectural-proposals/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 architectural-proposals Skill
- Use it for documentation.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/aitour26-BRK445-building-enterprise-ready-ai-agents-with-microsoft-foundry
- Skill file: .copilot/skills/architectural-proposals/SKILL.md
What it does
How to write comprehensive architectural proposals that drive alignment before code is written
Skill instructions
Context Proposals create alignment before code is written. Cheaper to change a doc than refactor code. Use this pattern when: - Architecture shifts invalidate existing assumptions - Product direction changes require new foundation - Multiple waves/milestones will be affected by a decision - External dependencies (Copilot CLI, SDK APIs) change Patterns Proposal Structure (docs/proposals/) Required sections: 1. Problem Statement — Why current state is broken (specific, measurable evidence) 2. Proposed Architecture — Solution with technical specifics (not hand-waving) 3. What Changes — Impact on existing work (waves, milestones, modules) 4. What Stays the Same — Preserve existing functionality (no regression) 5. Key Decisions Needed — Explicit choices with recommendations 6. Risks and Mitigations — Likelihood + impact + mitigation strategy 7. Scope — What's in v1, what's deferred (timeline clarity) Optional sections: - Implementation Plan (high-level milestones) - Success Criteria (measur
Verified compatibility and discovery
Frequently asked questions
What is architectural-proposals?
architectural-proposals is a open-source AI agent skill with Copy skill directory. How to write comprehensive architectural proposals that drive alignment before code is written
Who is architectural-proposals best for?
architectural-proposals is best for reusing agent instructions, scripts, and references, documentation workflows, writing workflows.
How do I install architectural-proposals?
Install or run architectural-proposals using Copy skill directory. Check architectural-proposals for the latest setup command.
Is architectural-proposals actively maintained?
architectural-proposals 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.
