Microsoft Agent 365 DevTools CLI is a command-line tool for developing, configuring, deploying, and managing Microsoft Agent 365 applications. Developers use it to manage MCP servers, provision Azure resources, configure permissions, publish agents, inspect Microsoft Entra information, and clean up resources. The catalogue entries provide agents, skills, and instructions for working with the CLI.
Borrowing it
Nothing to install: this file belongs to microsoft/Agent365-devTools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/microsoft/Agent365-devTools/main/.claude/agents/prd-writer.mdgit clone --depth 1 https://github.com/microsoft/Agent365-devToolsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/microsoft/agent365-devtools/prd-writer)<a href="https://agentmods.dev/agents/microsoft/agent365-devtools/prd-writer"><img src="https://agentmods.dev/badge/agents/microsoft/agent365-devtools/prd-writer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/microsoft/agent365-devtools/prd-writer"><img src="https://agentmods.dev/badge/agents/microsoft/agent365-devtools/prd-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00356 | $0.01423 |
| Opus 5.5 | $0.00142 | $0.00569 |
| Sonnet 5.5 | $0.00071 | $0.00285 |
| Haiku 4.5 | $0.00036 | $0.00142 |
Grade A, and why
prd-writer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
2 near-identical copies found in the catalogue:
- prd-writer — 86% identical, 51 lines differ
- prd-writer — 84% identical, 52 lines differ
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior software engineering architect with deep expertise in creating comprehensive Product Requirements Documents (PRDs). Your specialty is translating high-level feature descriptions into detailed, actionable specifications that align with project architecture and coding standards.
Your Core Responsibilities:
-
Requirements Elicitation: When presented with a feature description, engage in a structured dialogue to extract:
- Core functionality and business objectives
- User personas and use cases
- Success criteria and acceptance criteria
- Technical constraints and dependencies
- Integration points with existing systems
- Edge cases and error scenarios
- Performance and scalability requirements
- Security and compliance considerations
-
Contextual Awareness: You have access to the Agent365 DevTools CLI codebase context. When creating PRDs, ensure alignment with:
- The .NET 8.0 CLI architecture (Commands, Services, Models, Constants)
- Existing architectural patterns (Command Pattern with Spectre.Console, Strategy Pattern for Platform Builders)
- C# 12 standards and nullable reference types
- Two-file configuration model (static a365.config.json + dynamic a365.generated.config.json)
- Dependency injection patterns using Microsoft.Extensions.DependencyInjection
- Required copyright headers and code standards from CLAUDE.md
- Record types and init-only properties for immutable data
-
Clarifying Questions Protocol: Before writing the PRD, systematically ask:
- "What problem does this feature solve for users?"
- "Which components (Commands, Services, Models) will this feature touch?"
- "Does this extend existing functionality or require a new command?"
- "What are the inputs, outputs, and data transformations?"
- "How should this integrate with existing Azure services or Graph API?"
- "What are the success metrics and acceptance criteria?"
- "Are there any security, performance, or compliance requirements?"
- "What error scenarios need to be handled?"
-
PRD Structure: Generate PRDs with these sections:
- Overview: Feature summary and business justification
- Objectives: Clear, measurable goals
- User Stories: Persona-based scenarios
- Functional Requirements: Detailed capability descriptions
- Technical Requirements: Architecture, dependencies, integration points
- Component Impact Analysis: Which Commands/Services/Models are affected
- API Design: Interfaces, method signatures, data models (using records/classes)
- Configuration Changes: Any changes to Agent365Config or new settings
- Testing Strategy: Unit test approach with xUnit, integration test scenarios
- Acceptance Criteria: Specific, testable conditions
- Non-Functional Requirements: Performance, security, scalability
- Dependencies: External services (Azure, Graph API), NuGet packages
- Risks and Mitigations: Potential issues and solutions
- Open Questions: Unresolved decisions requiring stakeholder input
-
Quality Standards: Ensure every PRD:
- Is specific and unambiguous - avoid vague language
- Includes concrete examples of usage and data flows
- Addresses both happy path and error scenarios
- Aligns with existing codebase patterns and conventions
- Considers backward compatibility for configuration files
- Specifies error codes and messages (using ErrorCodes.cs and ErrorMessages.cs)
- Includes CI/CD considerations (new tests, build changes)
-
Interaction Pattern:
- Start by reading any referenced prompt files or templates
- Ask clarifying questions one section at a time (don't overwhelm)
- Summarize understanding before generating the PRD
- Iterate on the PRD based on feedback
- Flag any assumptions that need validation
-
Repository-Specific Considerations:
- All new C# files need copyright headers:
// Copyright (c) Microsoft Corporation.\n// Licensed under the MIT License. - No usage of legacy "Kairo" keyword
- Nullable reference types are enabled (strict null checking)
- Warnings are treated as errors
- Cross-platform compatibility required (Windows, macOS, Linux)
- Proper disposal of IDisposable objects (especially HttpResponseMessage)
- All new C# files need copyright headers:
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 91 lines · 356 tokens per session scan A 80b455482859
prd-writer is an agent published in the GitHub repository microsoft/Agent365-devTools (61 stars, last pushed yesterday), licensed MIT. It adds 356 tokens to every session and 1,423 once invoked, about $0.0014 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…