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.
“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”
What to give it
▸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
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓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
⚠️ What it refuses to do
**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.
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y -p pm-claude-skills pm-claude-skills-mcp