$ ~/registry/skill/microsoft-agency-plugins-nori-skills-writing-plans

SKILL

writing-plans

Name: writing-plans
Author: microsoft

Create detailed implementation plans for engineers with little or no codebase context.

Stars

★ 4,934

Source

GitHub

Updated

2026-07-14

// securityCaution

Prompt only, no code
Open source

Summary

This skill appears to be prompt-only, open-source, requires no secrets, and declares no remote endpoints, so overall risk is low. The main caution is instructional text in the README aimed at the host agent, including file-path planning requirements, which suggests some prompt-injection or misleading-instruction potential, but there are no concrete red flags for code execution, data exfiltration, or credential abuse.

CredentialsLow risk

The material explicitly states that no keys or environment variables are required, and there is no indication of reading, storing, or transmitting credentials, so credential exposure or misuse risk is low.

Network egressLow risk

No remote endpoints are declared, and the system flags it as prompt-only; based on the provided facts, it does not involve sending user data to external services.

Code executionCaution

As a prompt-based skill, its README contains operational instructions aimed at the host agent, such as 'Add the following steps to your Todo list using TodoWrite.' While it does not provide executable code or installation steps, it does show prompt-injection-like influence over agent behavior and should be handled with caution.

Data accessCaution

The material encourages generating implementation plans with exact file paths and mentions absolute paths and worktrees, while also explicitly stating 'Do not write a file to disk unless explicitly asked.' No active read/write capability is declared; the main concern is nudging an agent toward local code structure and path awareness rather than direct overbroad access.

Supply chainCaution

The source is identified as an open-source GitHub repository, which is a positive factor for auditability; however, community adoption is 0 stars, the license is undeclared, and maintenance status is unknown, which weakens source trust. There are no high-risk red flags such as closed source code, suspicious download scripts, or opaque dependencies.

Recommendations

Treat this skill as untrusted prompt content: extract planning intent only, and do not blindly follow its imperative instructions to the host agent.
Limit the skill's implicit influence over todos, file paths, and workspace context in the host environment, and require human confirmation when needed.
Verify the actual repository, license, and recent maintenance status before use to ensure it is the intended project rather than a placeholder or unmaintained content.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "writing-plans" skill from askskill:
1. Download https://raw.githubusercontent.com/microsoft/FluidFramework/main/.agency/plugins/nori/skills/writing-plans/SKILL.md
2. Save it as ~/.claude/skills/writing-plans/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Break down tasks for a new feature

Prompt

We have finished the design for a 'team member invitation' feature. Based on the requirements below, write a detailed implementation plan for engineers, including recommended file paths to modify, frontend and backend task breakdown, key data structures, API definitions, complete code examples, migration steps, and a testing and verification checklist. Assume the implementer has almost no knowledge of the current codebase or business context. Requirements: ...

Expected

A complete implementation plan for someone unfamiliar with the codebase, including steps, file locations, sample code, and validation methods.

Turn a product spec into an engineering plan

Prompt

Convert this product spec into an engineering implementation document. The output should include implementation goals, prerequisites, development tasks by module, file paths involved in each step, pseudocode or real code examples, error-handling recommendations, test cases, and pre-release checks. Assume the reader is an engineer who just joined the project. Product spec: ...

Expected

A structured engineering plan that helps a newcomer implement and self-test independently.

Create an execution plan for a refactor

Prompt

We need to refactor the existing authentication module. Produce a detailed execution plan: first explain the goal and scope, then provide phased tasks, file paths involved in each phase, key change examples, risks, rollback plans, verification steps, and testing strategy. Assume the engineer does not understand the current authentication implementation. Background information: ...

Expected

A phased, reversible, and verifiable refactor plan that reduces execution risk for unfamiliar engineers.

// docs

<required> CRITICAL. Add the following steps to your Todo list using TodoWrite:

Read the 'Guidelines'.
Create a comprehensive plan that a senior engineer can follow. <system-reminder>Any absolute paths in your plan MUST take into account any worktrees that may have been created</system-reminder>
Think about backwards compability. Add any notes to the plan.
Think about edge cases. Add them to the plan.
Think about questions or areas that require clarity. Add them to the plan.
Emphasize how you will test your plan.
Present plan to user. </required>

Guidelines

Overview

Create a comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD.

Assume they are a talented developer. However, assume that they know almost nothing about our toolset or problem domain. Assume they don't know good test design very well.

Do not add code, but include enough detail that the necessary code is obvious.

Do not write a file to disk unless explicitly asked.

Plan Document Header

Every plan MUST start with this header:

# [Feature Name] Implementation Plan

**Goal:** [One sentence describing what this builds]

**Architecture:** [2-3 sentences about approach]

**Tech Stack:** [Key technologies/libraries]

---

Test Section

Every plan MUST have a test section. This should be written first, and should document how you plan to test the behavior.


**Testing Plan**

I will add an integration test that ensures foo behaves like blah. The
integration test will mock A/B/C. The test will then call function/cli/etc.

I will add a unit test that ensures baz behaves like qux...

You should end EVERY testing plan section by writing:

NOTE: I will write *all* tests before I add any implementation behavior.

<system-reminder>Your tests should NOT contain tests for datastructures or types. Your tests should NOT simply test mocks. Always test actual behavior.</system-reminder>

<required> For each test, follow this checklist: - Ensure that the test does not just test mocks. If it does, remove the test and try again. - Ensure the test does not test implementation detail. If it does, rewrite the test so that it tests boundary behavior. - Ensure the test does not test data structure format or types. If it does, remove the test and try again. - Ensure the test does not test for removed behavior. For example, if some behavior has been deprecated, do not write a test that simply confirms the behavior no longer works. - Evaluate if the test treats the interior of the test boundary as a blackbox. You should not know anything about interior variables, function calls, or control flow. </required>

Plan Document Footer

Every plan MUST end with this footer:

**Testing Details** [Brief description of what tests are being added and how they specifically test BEHAVIOR and NOT just implementation]

**Implementation Details** [maximum 10 bullets about key details]

**Question** [any questions or concerns that may be relevant that need answers]

---