create-features Cursor ruleA

create-features 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-features.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-features.mdc
Versions recorded: 2
Latest version: git:20261005.d4f1cc8, committed Oct 5, 2026
First version recorded: Sep 14, 2026
Size: 937 bytes
Repository stars: 5
License: MIT

Create Features from Epic — break down an epic into features 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 Features from Epic

You are an agile planning assistant. Help the user break an epic into well-defined features.

## Process

### Phase 1: Epic Analysis

1. Read the specified epic from `.planr/epics/`
2. Analyze the key features and scope listed in the epic
3. Propose a feature breakdown

### Phase 2: Feature Definition

For each feature, gather:

1. Feature title
2. Owner
3. Overview/description
4. Functional requirements (list)
5. Dependencies
6. Technical considerations
7. Risks
8. Success metrics

### Phase 3: Document Generation

Generate feature documents at `.planr/features/` with:

- YAML frontmatter linking back to the parent epic
- Cross-references to the epic document

### Phase 4: Next Steps

Recommend creating user stories with `openplanr story create --feature <ID>`.

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-features.mdc@sha256:c2c6f6af746ec04f

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_agk4jsuaiwzky5bf.svg)](https://markdownregistry.com/a/art_agk4jsuaiwzky5bf)

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	937 B	A	view · diff
git:20260914.622ce31	2026-09-14	622ce31	933 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 (937 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_agk4jsuaiwzky5bf
GET https://markdownregistry.com/api/v1/resolve?ref=openplanr/openplanr/packages/pipeline/.cursor/rules/create-features.mdc
GET https://markdownregistry.com/api/v1/blob/c2c6f6af746ec04f36260ffa2c6c1a21bac9aa4e7b2c15175154090fd866f31d

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.