writing-plans SKILL.md skillA

writing-plans from summerengine/summer is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add summerengine/summer/writing-plans@git:20261010.4ade947

Pins git:20261010.4ade947 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: summerengine/summer
Path: library/skills/writing-plans/SKILL.md
Versions recorded: 5
Latest version: git:20261010.4ade947, committed Oct 10, 2026
First version recorded: Sep 1, 2026
Size: 6,689 bytes
Repository stars: 86
License: MIT

Turn a spec or requirements for a multi-step task into a written implementation plan before touching code.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Writing Plans

## Overview

Write 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. Frequent commits.

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

**Announce at start:** "I'm using the writing-plans skill to create the implementation plan."

**Context:** If the work needs isolation from the current checkout, create a git worktree for it before execution starts.

**Save plans to:** `.summer/plans/YYYY-MM-DD-<feature-name>.md` in the game project
- (User preferences for plan location override this default)

## Scope Check

If the spec covers multiple independent subsystems, it should have been broken into sub-project specs during brainstorming. If it wasn't, suggest breaking this into separate plans — one per subsystem. Each plan should produce working, testable software on its own.

## File Structure
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add summerengine/summer/writing-plans@sha256:116886b5118cc644

The line at the top of this page pins the label git:20261010.4ade947, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_4ybvstntxq7ipijx.svg)](https://markdownregistry.com/a/art_4ybvstntxq7ipijx)

1 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 5 versions of this file, between Sep 1, 2026 and Oct 10, 2026, about one every 10 days.

version	committed	commit	size	audit
git:20261010.4ade947 latest	2026-10-10	4ade947	6,689 B	A	view · diff
git:20260911.b4df358	2026-09-11	b4df358	6,676 B	A	view · diff
git:20260910.4dc9f27	2026-09-10	4dc9f27	6,652 B	A	view · diff
git:20260902.548800b	2026-09-02	548800b	6,400 B	A	view · diff
git:20260901.7eb75a2	2026-09-01	7eb75a2	6,414 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (6689 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

summerengine/summer · 86 stars · license MIT · pushed 2026-10-20 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_4ybvstntxq7ipijx
GET https://markdownregistry.com/api/v1/resolve?ref=summerengine/summer/writing-plans
GET https://markdownregistry.com/api/v1/blob/116886b5118cc644d3b6d31a14a5eb8f28592af2114ea4f634f2778b5d382ade

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from summerengine/summer

AGENTS.md AGENTS.md file

summerengine/summer · AGENTS.md

git:20261010.8edeb3f · audit A · 86 stars

3d-lighting SKILL.md skill

summerengine/summer · library/skills/3d-lighting/SKILL.md · Set up 3D scene lighting — DirectionalLight3D vs Omni vs Spot, WorldEnvironment, sky, shadow tuning, ambient — per…