create-epic Cursor ruleA

create-epic from openplanr/openplanr is a Cursor rule: instructions the Cursor agent follows in that repo.

Install it, pinned

mdr add openplanr/openplanr/packages/pipeline/.cursor/rules/create-epic.mdc@git:20261005.d4f1cc8

Pins git:20261005.d4f1cc8 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 14 of 14 checks passed
Kind: Cursor rule
Repository: openplanr/openplanr
Path: packages/pipeline/.cursor/rules/create-epic.mdc
Versions recorded: 2
Latest version: git:20261005.d4f1cc8, committed Oct 5, 2026
First version recorded: Sep 14, 2026
Size: 1,095 bytes
Repository stars: 5
License: MIT

Create an Epic — conversational epic creation for planr-pipeline.

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

# Create an Epic

You are an agile planning assistant. Help the user create a well-structured epic.

## Process

### Phase 1: Information Gathering

Ask these questions one at a time:

1. What is the epic title?
2. Who owns this epic?
3. What is the business value?
4. Who are the target users?
5. What problem does this solve?
6. What is the proposed solution?
7. What are the success criteria?
8. What are the key features (list)?
9. What dependencies exist?
10. What are the risks?

### Phase 2: Document Generation

Generate the epic document at `.planr/epics/` using this structure:

- YAML frontmatter with id, title, owner, dates, status
- Sections: Business Value, Target Users, Problem Statement, Solution Overview, Success Criteria, Key Features, Dependencies, Risks

### Phase 3: Next Steps

Recommend creating features from this epic using `openplanr feature create --epic <ID>`.

## Existing Epics

Check `.planr/epics/` for existing epics to avoid duplication.

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add openplanr/openplanr/packages/pipeline/.cursor/rules/create-epic.mdc@sha256:b88fd528db441ffb

The line at the top of this page pins the label git:20261005.d4f1cc8, 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_qtofgz2chwn2nqjb.svg)](https://markdownregistry.com/a/art_qtofgz2chwn2nqjb)

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

Versions

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

version	committed	commit	size	audit
git:20261005.d4f1cc8 latest	2026-10-05	d4f1cc8	1,095 B	A	view · diff
git:20260914.622ce31	2026-09-14	622ce31	1,091 B	A	view

Audit of the latest version

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

pass: Size between 200 bytes and 200 KB (1095 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

openplanr/openplanr · 5 stars · license MIT · pushed 2026-10-20 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_qtofgz2chwn2nqjb
GET https://markdownregistry.com/api/v1/resolve?ref=openplanr/openplanr/packages/pipeline/.cursor/rules/create-epic.mdc
GET https://markdownregistry.com/api/v1/blob/b88fd528db441ffb1399856063871b5dac26cdc6aee4a9b5bc087822bc4ad282

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: Cursor rules vs AGENTS.md · which agent file does what.