llp-list
Skill16 starsChanged 3 months agoMITView on GitHub
List the LLP documents in this repository, grouped by status or filtered by type, system, or status. Useful for answering "what's still in draft?", "which RFCs are active?", or "what documents cover the auth system?
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- llp-createSkill
- llp-grillSkill
- llp-init-retrofitSkill
- llp-initSkill
- llp-reviewSkill
- ref-checkSkill
- ref-storySkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 8 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when the user wants to see what LLPs exist in the repo, or filter them by type, status, or system tag.
- Distinctive: line 36
Read the file header and extract:
- Distinctive: line 52
If the user specified filters, remove LLPs that don't match.
- Distinctive: line 59
If no filter is provided, show everything.
- Distinctive: line 67
If a single-status filter was provided, skip grouping and just show the sorted list.
- Distinctive: line 93
If a filter was provided, include the filter in the header:
- Very specific: line 125
Files without a parseable header: If the metadata is missing or malformed, include the file in the output but mark its fields as (unknown).
- Distinctive: line 126
Duplicate numbers: Should never happen but may if someone made a mistake.
- Distinctive: line 131
Do not create, modify, or delete LLPs.
- Very specific: line 132
Do not interpret LLP content: just metadata.
- Very specific: line 133
Do not follow cross-references (Related: fields).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
llp-list
Use this skill when the user wants to see what LLPs exist in the repo, or filter them by type, status, or system tag.
Invoke as:
/llp-list: show all LLPs grouped by status/llp-list <status>: show only LLPs with that status (e.g.,/llp-list draft,/llp-list active)/llp-list type=<type>: show only LLPs of a given type (e.g.,/llp-list type=rfc)/llp-list system=<system>: show only LLPs tagged with a given system/llp-list author=<name>: show LLPs by a specific author
Filters can combine: /llp-list draft type=rfc system=auth.
Ground rules
- LLPs live in
llp/by default. Scan recursively, includingllp/tombstones/. - Other repositories may have additional LLP trees; check the project's root LLP,
CLAUDE.md, orAGENTS.mdfor documented locations. - LLP filenames follow
NNNN-slug.type.md. The number and type come from the filename; title, status, systems, and author come from the metadata header at the top of the file. - Standard statuses:
Draft,Review,Accepted,Active,Superseded,Tombstoned. - Standard types:
rfc,spec,decision,plan,explainer,principle,guide,issue,research.
Workflow
1. Scan and parse
Walk the llp/ directory. For each file matching NNNN-*.md:
- Extract the number from the filename prefix.
- Extract the type from the filename extension (the segment before
.md). - Read the file header and extract:
- Title from the first
# LLP NNNN: <Title>heading line - Status from
**Status:** <value> - Systems from
**Systems:** <comma-separated list> - Author from
**Author:** <value> - Date from
**Date:** <value>
- Title from the first
Normalize values:
- Strip leading/trailing whitespace
- Strip
vNsuffixes on statuses (e.g.,Draft v2→Draft) - Strip trailing parenthetical notes (e.g.,
Accepted (pending implementation)→Accepted) - Compare case-insensitively
2. Apply filters
If the user specified filters, remove LLPs that don't match. Supported filters:
- Status: case-insensitive exact match after normalization
- Type: case-insensitive exact match
- System: case-insensitive substring match against the Systems list
- Author: case-insensitive substring match against the Author field
If no filter is provided, show everything.
3. Group and sort
Group by status (in the canonical lifecycle order: Draft → Review → Accepted → Active → Superseded → Tombstoned → any other / unknown statuses at the end).
Within each group, sort by LLP number ascending.
If a single-status filter was provided, skip grouping and just show the sorted list.
4. Render
Format each LLP as:
NNNN <title> [<type>] <systems>With fixed-width number column and visually separated fields. Example:
DRAFT
0041 Network error handling [rfc] Network
0045 Offline queue design [rfc] Sync, Offline
0047 Intent-level authoring [research] SDK
ACTIVE
0001 Greenfield setup [guide] Core
0004 Design principles [principle] Core
TOMBSTONED
0009 Legacy sync design [decision] SyncIf a filter was provided, include the filter in the header:
Draft LLPs tagged "auth":
0042 Token rotation [rfc] Auth, Security
0044 Session management [rfc] Auth5. Summary line at the end
Show a count:
42 LLPs: 8 draft, 2 review, 4 accepted, 26 active, 2 supersededOr for filtered results:
3 matching LLPs (2 draft, 1 review)Output formats
By default, render as plain text. Support format flags:
/llp-list --format=json: emit a JSON array of LLP metadata for programmatic use/llp-list --format=markdown: emit a markdown-formatted list, suitable for pasting into another document/llp-list --format=table: emit a markdown table with Number / Title / Type / Status / Systems columns
Edge cases
- Files without a parseable header. If the metadata is missing or malformed, include the file in the output but mark its fields as
(unknown). Report a count of problem files at the end. - Duplicate numbers. Should never happen but may if someone made a mistake. List all files with duplicate numbers in a warning section at the end.
- Tombstones directory. Files in
llp/tombstones/should be included in the listing but their default status isTombstonedeven if the file header says otherwise (the location is authoritative for tombstoned status). Filtertombstonedto show only these; by default they appear in the tombstoned group.
Scope limits
- Do not create, modify, or delete LLPs. This skill is read-only.
- Do not interpret LLP content: just metadata. For content analysis, use
/llp-searchor/llp-review. - Do not follow cross-references (
Related:fields). For cross-reference traversal, use/llp-related.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

