Writing Plan Documents
Use when writing any plan document or product spec — project plans, PRDs, product specs, proposals, implementation plans, or design docs. Applies ASD-STE100 Simplified Technical English as a writing style layer alongside other planning skills like superpowers:writing-plans.
Install
/plugin marketplace add borkweb/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add borkweb/skills --skill writing-plan-documentsgit clone --depth 1 https://github.com/borkweb/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/core/writing-plans ~/.claude/skills/writing-plan-documentsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Writing Plan Documents Apply this prose layer within the task's chosen planning workflow. Inherit the active model and reasoning effort. - Write all prose to the ASD-STE100 rules in [ste100.md](ste100.md). Read that file before the first write. If another prose skill runs on the same document, the STE rules control sentence form. - Write for someone who has not seen the conversation. Lead with the goal and decisions; follow with the rationale needed to assess them. - Use concrete actions and accurate uncertainty. Remove filler, inflated adjectives, theatrical reveals, contrastive setups and summaries that repeat the preceding text. - Include only sections that help the reader act: scope, approach, dependencies, risks, unresolved decisions and acceptance criteria as relevant. Preserve another workflow's required structure. - For an unresolved decision, name the choice, viable options and tradeoffs, then recommend an option when evidence supports it. Do not invent alternatives for settled or trivial choices. - Sequence milestones by dependencies and outputs. Preserve real deadlines or a requested schedule; label uncertain estimates and separate coding time from review or rollout elapsed time. Do not fabricate calendar commitments. - Keep lists for parallel items and prose for relationships. A heading or paragraph must add information. - For a long document, write a skeleton first, then add or edit one section per write so no single response approaches the output limit.
Details
- Skill name
writing-plan-documents- Repository
- borkweb/skills
- Path
skills/core/writing-plans/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Writing Plan Documents skill do?
Use when writing any plan document or product spec — project plans, PRDs, product specs, proposals, implementation plans, or design docs. Applies ASD-STE100 Simplified Technical English as a writing style layer alongside other planning skills like superpowers:writing-plans.
How do I install the Writing Plan Documents skill?
Claude Code plugin: /plugin marketplace add borkweb/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Writing Plan Documents popular?
It lives in borkweb/skills, which has 9 GitHub stars and 0 forks.
Related skills
Prototype
9borkweb/skills
Build a throwaway prototype to flesh out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".
Agents Md Lint
9borkweb/skills
Audit and trim AI agent instruction files (AGENTS.md, CLAUDE.md, CONVENTIONS.md, .cursorrules, etc.) by testing which facts an AI agent can discover from code alone. Use when asked to lint, audit, optimize, prune, or trim any agent instruction file in a repository. Removes redundant documentation that wastes context tokens. Supports a dry-run mode that reports findings without modifying files.
Auto Scope
9borkweb/skills
Scopes a coding task before implementation — names the handful of files actually relevant (read/edit these), the areas to leave alone, and any open scope questions, so work doesn't start by reading the whole repo. Fires proactively at the start of substantive, multi-file, or unfamiliar-area work; stays silent on single-file edits, one-line fixes, questions, and continued work in an area already scoped this session. Use when beginning a feature, bug fix, or refactor that could plausibly touch several files or an area not yet seen this session.
Adhx
9huytran1120/vietnam-agentic-skills
Fetch any X/Twitter post as clean LLM-friendly JSON. Converts x.com, twitter.com, or adhx.com links into structured data with full article content, author info, and engagement metrics. No scraping or browser required.
Writing Commits
9borkweb/skills
Create an authorized git commit or draft its message, grounded in the intended diff and repository conventions. Message-only requests never commit; commit requests do not imply push or merge.
Proposal Writing
6MarcoZorn/agencykit
Generate a client proposal from scope, budget and past project references. Draws from scope/outcome example pairs when provided.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.