to-issues skillA
to-issues is agent-read markdown (skill) from serejaris/personal-corp-os: Break a plan, spec, or PRD into independently-grabbable task files using tracer-bullet vertical slices..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# To Issues Break a plan into independently-grabbable task files using vertical slices (tracer bullets). ## Process ### 1. Gather context Work from whatever is already in the conversation context. If `PRD.md` exists in the project folder root, read it in full. If the user points at another spec file, read that instead. ### 2. Explore the codebase (optional) If you have not already explored the codebase, do so to understand the current state of the code. Task titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching. Look for opportunities to prefactor the code to make the implementation easier. "Make the change easy, then make the easy change." ### 3. Draft vertical slices Break the plan into **tracer bullet** tasks. Each task is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer. <vertical-slice-rules> - Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests) - A completed slice is demoable or verifiable on its own - Any prefactoring should be done first </vertical-slice-rules> ### 4. Quiz the user …
Read the whole file at its exact version.
How to install
mdr add serejaris/personal-corp-os/to-issues@git:20260709.553b137mdr add serejaris/personal-corp-os/to-issues@sha256:b11dc308fc679263Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_vat2fpzvsqyrizau)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3159 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
serejaris/personal-corp-os · 228 stars · license MIT · pushed 2026-09-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vat2fpzvsqyrizau GET https://markdownregistry.com/api/v1/resolve?ref=serejaris/personal-corp-os/to-issues GET https://markdownregistry.com/api/v1/blob/b11dc308fc679263f3bb7f2d5d7c84ea7cac6016ee99989b0ffac88e4f60a761
Your agent 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.
More from serejaris/personal-corp-os
Every file in serejaris/personal-corp-os