New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Planning Application Statement

by mohitagw15856 in mohitagw15856/pm-claude-skills

Write the design and access statement that supports a planning application — the site analysis, the design rationale, the policy compliance, and the answers to the objections the case officer will…

MITAuto-check passed

Install Planning Application Statement

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill planning-application-statement -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills planning-application-statement --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/planning-application-statement .claude/skills/planning-application-statement && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
planning-application-statement
GitHub stars
1.4k
Token cost
~1.6k tokens
SKILL.md length
742 words
Files
1
Skills in repo
1,322
Repo updated
First seen
Licence
MIT

At a glance

Write the design and access statement that supports a planning application — the site analysis, the design rationale, the policy compliance, and the answers to the objections the case officer will…

  • Works in 6 steps: Analyse the site before describing the… → Show the design evolving. Including the… → Address policies by their number and… → …
  • Asked to write a design and access statement
  • SKILL.md covers What This Skill Produces, Required Inputs, Framework: Analysis, Then… and Output Format, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Planning Application Statement is an agent skill from mohitagw15856/pm-claude-skills. Write the design and access statement that supports a planning application — the site analysis, the design rationale, the policy compliance, and the answers to the objections the case officer will receive. Use when asked to write a design and access statement, planning statement, or supporting statement for a planning application, or to respond to a planning objection or refusal. Produces the site and context analysis, the design evolution narrative, the policy-by-policy compliance table, the access and amenity…

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Asked to write a design and access statement
  • Planning statement
  • Supporting statement for a planning application
  • Respond to a planning objection

Example prompts

  • “/planning-application-statement”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Analyse the site before describing the scheme. Character, scale, materials, topography, boundaries, and how the site is actually used. A…
  2. Show the design evolving. Including the option you rejected and why. Officers trust a scheme that visibly responded to constraints more…
  3. Address policies by their number and name. A general claim of compliance forces the officer to do the work, and they will do it less…
  4. Answer amenity concretely. Distances, angles, and hours — not 'no undue impact'. Overlooking and overshadowing are measurable and should…
  5. Pre-empt the objections you know are coming. Parking, overlooking, precedent, construction disturbance. Addressed in the statement, they…
  6. Be accurate about what is proposed. A discrepancy between the statement and the drawings costs credibility for the whole application.

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Planning Application Statement loads about 1.6k tokens when it runs. Until then it costs about 164 tokens; SKILL.md has 742 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~164
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 742 words, ~1,582 tokens.

Download SKILL.mdSave it as .claude/skills/planning-application-statement/SKILL.md (or your agent's skills folder).
name
planning-application-statement
description
Write the design and access statement that supports a planning application — the site analysis, the design rationale, the policy compliance, and the answers to the objections the case officer will receive. Use when asked to write a design and access statement, planning statement, or supporting statement for a planning application, or to respond to a planning objection or refusal. Produces the site and context analysis, the design evolution narrative, the policy-by-policy compliance table, the access and amenity assessment, and the pre-empted objections. Not planning or legal advice; local policy and procedure govern.

Planning Application Statement

A case officer reads dozens of these. What they need is to find, quickly, that you have understood the site, that the design follows from that understanding, and that each relevant policy is addressed by name. What they get is usually a description of the proposal. This writes the version that answers their report for them — and pre-empts the objections that will land in the consultation period.

What This Skill Produces

  • Site and context analysis — what is actually there, what characterises it, and what the site can take
  • The design rationale — how the proposal follows from the analysis, including what was tried and rejected
  • A policy compliance table — each relevant local and national policy, named, with how the scheme complies
  • Access and amenity assessment — inclusive access, overlooking, overshadowing, noise, parking, and refuse
  • Pre-empted objections — the concerns neighbours will raise, addressed before they are raised
  • The consultation record — pre-application advice and any engagement already undertaken

Required Inputs

Ask for these if not provided:

  • The proposal — what is being applied for, with areas, heights, and materials
  • The site — location, existing use, constraints, designations, boundaries, and neighbouring context
  • The policy framework — the local plan policies and any supplementary guidance that apply
  • Pre-application history — any advice received, and previous applications or refusals on the site
  • The known sensitivities — what neighbours or the parish have objected to before

Framework: Analysis, Then Rationale, Then Policy by Name

  1. Analyse the site before describing the scheme. Character, scale, materials, topography, boundaries, and how the site is actually used. A rationale unearned by analysis reads as post-hoc justification.
  2. Show the design evolving. Including the option you rejected and why. Officers trust a scheme that visibly responded to constraints more than one presented as inevitable.
  3. Address policies by their number and name. A general claim of compliance forces the officer to do the work, and they will do it less generously than you would.
  4. Answer amenity concretely. Distances, angles, and hours — not 'no undue impact'. Overlooking and overshadowing are measurable and should be measured.
  5. Pre-empt the objections you know are coming. Parking, overlooking, precedent, construction disturbance. Addressed in the statement, they arrive at the officer already answered.
  6. Be accurate about what is proposed. A discrepancy between the statement and the drawings costs credibility for the whole application.

Output Format

Show full SKILL.md (354 more words)Show less
Design & access statement: [proposal] · [site] · [date]

Proposal: [precise description matching the application form and drawings]

Site & context: [existing use, area, boundaries, topography, access] · Character: [what defines the surrounding area — scale, materials, grain, roofline] · Designations: [conservation area, listed, flood zone, TPO, green belt, or none]

Design evolution

Option consideredWhy rejected
[option][reason]
Adopted approach: [how it responds to the analysis above — scale, siting, materials, roofline]

Policy compliance

PolicyRequirementHow the proposal complies
[ref & name][what it requires][specific response]

Access: [inclusive access, approach, entrance, level changes, parking including accessible spaces, refuse and cycle storage]

Amenity: overlooking [distances, window positions, screening] · overshadowing [orientation, separation, any daylight assessment] · noise [source, mitigation] · construction [hours, access, management]

Anticipated concerns, addressed

  • [likely objection] — [the specific response]

Pre-application: [advice received, reference, and how the scheme responded] · Engagement: [what was done]

Supporting-document drafting only, not planning or legal advice. Local plan policies, validation requirements, consultation procedure and appeal rights differ by authority and change — verify everything against the current local plan and the authority's own validation checklist before submission.

Quality Checks

  • Site analysis precedes and demonstrably drives the design rationale
  • At least one rejected option is shown, with its reason
  • Every relevant policy is named by reference, not addressed generically
  • Amenity impacts are quantified with distances and orientation
  • The likely objections are answered inside the statement
  • The description matches the drawings and application form exactly

Anti-Patterns

  • Describing the proposal instead of justifying it. The officer already has the drawings.
  • Claiming policy compliance in general. Unnamed policies get assessed without your help.
  • 'No undue impact on amenity'. Meaningless without distances; objectors will supply their own numbers.
  • A design with no rejected options. Reads as unconsidered, however good it is.
  • Ignoring the obvious objection. It arrives anyway, and now unanswered.
  • Statement and drawings disagreeing. One discrepancy undermines everything else in the document.

Example Trigger Phrases

  • "Write a design and access statement for a rear extension"
  • "Draft a planning statement for this application"
  • "How do I address the local plan policies in my statement?"
  • "Neighbours are objecting about overlooking — how do I answer that?"
  • "Write a supporting statement for a change of use"

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/planning-application-statement of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Planning Application Statement next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Planning Application Statement compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Planning Application Statement this skillmohitagw15856/pm-claude-skills1.4k—~1.6kAutomated safety check: PassMIT
Three-Statement Financial AnalysisHKUDS/Vibe-Trading35k—~1.2kAutomated safety check: PassMIT
Value Prop Statementsphuryn/pm-skills27k—~758Automated safety check: PassMIT
Monthly Closing Statementssickn33/agentic-awesome-skills47k1 repos~6.2kAutomated safety check: PassMIT
User-Centered Problem Statementdeanpeters/Product-Manager-Skills7.2k1 repos~2.7kAutomated safety check: PassCustom licence
Personal Statementaipoch/medical-research-skills2k—~2.2kAutomated safety check: PassMIT

Similar skills

  • Three-Statement Financial Analysis

    HKUDS/Vibe-Trading

    Reads the income statement, balance sheet and cash flow statement together to judge earnings quality, apply DuPont analysis and check 12 red-flag indicators for manipulation; Chinese text.

    35k GitHub stars~1.2k tokensUpdated yesterday
    Business, Finance & HRAuto-check passed

  • Value Prop Statements

    phuryn/pm-skills

    Generate value proposition statements for marketing, sales, and onboarding from existing value propositions.

    27k GitHub stars~758 tokensUpdated 24 days ago
    Marketing & SEOAuto-check passed

  • Monthly Closing Statements

    sickn33/agentic-awesome-skills

    Monthly closing register: period dates, cash/bank/party/inventory/TDS reconciliation flags, profit, receivables, payables, working capital, open adjustments and reviewer.

    47k GitHub starsUsed in 1 repo~6.2k tokens
    Business, Finance & HRAuto-check passed

  • User-Centered Problem Statement

    deanpeters/Product-Manager-Skills

    Writes a problem statement from the user's point of view, covering who is blocked, what they're trying to do, and how it feels.

    7.2k GitHub starsUsed in 1 repo~2.7k tokens
    Product & Project ManagementAuto-check passed

  • Personal Statement

    aipoch/medical-research-skills

    A skill your agent uses when writing medical school personal statements, residency application essays, fellowship statements, or graduate school admissions essays.

    2k GitHub stars~2.2k tokensUpdated 21 days ago
    Research & ScienceAuto-check passed

  • Geoffrey Moore Positioning Statement

    deanpeters/Product-Manager-Skills

    Drafts a Crossing the Chasm-style positioning statement that forces hard choices about target customer, category, and differentiation.

    7.2k GitHub starsUsed in 1 repo~2.6k tokens
    Marketing & SEOAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,322 skills in this repo

  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

  • Offer Comparison

    mohitagw15856/pm-claude-skills

    Compare two or more job offers as total-comp curves over four years — vesting cliffs, bonuses, 401(k) match, and the crossover year computed, not vibed.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Refinance Breakeven

    mohitagw15856/pm-claude-skills

    Compute the month a refinance actually starts saving money — payment delta, breakeven month, and total interest on both paths including the term-reset trap.

    1.4k GitHub stars~1k tokensUpdated yesterday
    Auto-check passed

  • Rent Vs Buy

    mohitagw15856/pm-claude-skills

    Model rent-vs-buy honestly — year-by-year net position for both paths including the assumption everyone drops (the renter invests the difference), with a breakeven horizon instead of a verdict.

    1.4k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Questions about Planning Application Statement

What does Planning Application Statement do?

Write the design and access statement that supports a planning application — the site analysis, the design rationale, the policy compliance, and the answers to the objections the case officer will…. Planning Application Statement is an agent skill from mohitagw15856/pm-claude-skills. Write the design and access statement that supports a planning application — the site analysis, the design rationale, the policy compliance, and the answers to the objections the case officer will receive.

When should I use Planning Application Statement?

Planning Application Statement fits situations like: asked to write a design and access statement; planning statement; supporting statement for a planning application; respond to a planning objection.

How do I install Planning Application Statement in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill planning-application-statement -a claude-code`. Or copy the skill folder (skills/planning-application-statement in mohitagw15856/pm-claude-skills) into .claude/skills/planning-application-statement in your project. Claude Code loads it when a task matches its description.

How do I install Planning Application Statement in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill planning-application-statement -a codex`. Or copy the skill folder (skills/planning-application-statement in mohitagw15856/pm-claude-skills) into .agents/skills/planning-application-statement in your project. Codex loads it when a task matches its description.

Can I use Planning Application Statement in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill planning-application-statement -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/planning-application-statement, .gemini/skills/planning-application-statement, .github/skills/planning-application-statement and .opencode/skills/planning-application-statement in your project.

What does Planning Application Statement need to run?

SKILL.md names no scripts, command-line tools or credentials: Planning Application Statement is instructions for the agent only.

Does Planning Application Statement access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Planning Application Statement safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Planning Application Statement use?

Planning Application Statement is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Planning Application Statement use?

About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Planning Application Statement?

Skills that share tags, products or a category with Planning Application Statement: Three-Statement Financial Analysis (HKUDS/Vibe-Trading, 35k stars), Value Prop Statements (phuryn/pm-skills, 27k stars), Monthly Closing Statements (sickn33/agentic-awesome-skills, 47k stars) and User-Centered Problem Statement (deanpeters/Product-Manager-Skills, 7.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Planning Application Statement?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,431 GitHub stars. The repository holds 1,322 skills in this directory. The repository was last updated on October 7, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.