planr-cto-review SKILL.md skillA

planr-cto-review from openplanr/openplanr is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add openplanr/openplanr/planr-cto-review@git:20261006.d2ef7a8

Pins git:20261006.d2ef7a8 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
openplanr/openplanr
Path
skills/planr-cto-review/SKILL.md
Versions recorded
5
Latest version
git:20261006.d2ef7a8, committed Oct 6, 2026
First version recorded
Sep 14, 2026
Size
2,190 bytes
Repository stars
5
License
MIT

Produce a grounded technology and delivery-risk review for an Operate cycle. Use when architecture, reliability, security, or execution risk needs a CTO lens.

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

# OpenPlanr CTO Review

## Shared contract

Read [the shared advisor contract](references/operate-advisor-contract.md) before reviewing. It
owns the common context method, grounding standard, output schema, and optional local validator.

## Role identity

- Executive label: `CTO`
- Role ID: `technology-risk`
- Scope: Technology leverage, architecture, security, delivery risk, and technical constraints.
- Capability ceiling: `read-only`

## Questions this lens must cover

1. Which technical constraints now block a stated objective?
2. Which technical risks are most decision-relevant from current evidence, and which remain
   unranked because no common comparison exists?
3. Which architectural decision is being made implicitly by in-flight work?
4. How reversible are the highest-impact evidenced changes?

## Evidence to seek

- Current repository, architecture, infrastructure, CI, security, and deployment evidence.
- Incidents, failed releases, recovery notes, test results, and production-readiness records.
- Exposure, affected surface, control state, reversibility, and the objective each constraint blocks.

## Decision standard
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add openplanr/openplanr/planr-cto-review@sha256:5fedb6d5d54d0d37

The line at the top of this page pins the label git:20261006.d2ef7a8, 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 badge

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

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

Versions

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

versioncommittedcommitsizeaudit
git:20261006.d2ef7a8 latest2026-10-06 d2ef7a8 2,190 BA view · diff
git:20261004.db8c0b92026-10-04 db8c0b9 2,251 BA view · diff
git:20260929.3e358fc2026-09-29 3e358fc 1,933 BA view · diff
git:20260928.382ce7c2026-09-28 382ce7c 1,986 BA view · diff
git:20260914.622ce312026-09-14 622ce31 1,966 BA 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 (2190 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_ilhrpuqhehgblwte
GET https://markdownregistry.com/api/v1/resolve?ref=openplanr/openplanr/planr-cto-review
GET https://markdownregistry.com/api/v1/blob/5fedb6d5d54d0d3762ff7ced1adcfb2c66bf237961991be290535f0b2027bce5

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 openplanr/openplanr

AGENTS.md@packages/cli AGENTS.md file
openplanr/openplanr · packages/cli/AGENTS.md
git:20260914.622ce31 · audit A · 5 stars
CLAUDE.md@packages/cli CLAUDE.md file
openplanr/openplanr · packages/cli/CLAUDE.md
git:20260914.622ce31 · audit A · 5 stars
agile-checklist Cursor rule
openplanr/openplanr · packages/pipeline/.cursor/rules/agile-checklist.mdc · Agile Development Checklist — guides you through the 5-phase agile workflow for planr-pipeline
git:20260914.622ce31 · audit A · 5 stars
create-epic Cursor rule
openplanr/openplanr · packages/pipeline/.cursor/rules/create-epic.mdc · Create an Epic — conversational epic creation for planr-pipeline
git:20261005.d4f1cc8 · audit A · 5 stars
create-features Cursor rule
openplanr/openplanr · packages/pipeline/.cursor/rules/create-features.mdc · Create Features from Epic — break down an epic into features for planr-pipeline
git:20261005.d4f1cc8 · audit A · 5 stars
create-task-list Cursor rule
openplanr/openplanr · packages/pipeline/.cursor/rules/create-task-list.mdc · Create Task List — generate implementation tasks from user stories for planr-pipeline
git:20260914.622ce31 · audit A · 5 stars
create-user-story Cursor rule
openplanr/openplanr · packages/pipeline/.cursor/rules/create-user-story.mdc · Create User Stories — generate user stories with Gherkin acceptance criteria for planr-pipeline
git:20261005.d4f1cc8 · audit A · 5 stars
implement-task-list Cursor rule
openplanr/openplanr · packages/pipeline/.cursor/rules/implement-task-list.mdc · Implement Task List — guidance-first implementation for planr-pipeline
git:20260914.622ce31 · audit A · 5 stars
AGENTS.md@packages/pipeline AGENTS.md file
openplanr/openplanr · packages/pipeline/AGENTS.md
git:20260914.622ce31 · audit A · 5 stars
CLAUDE.md@packages/pipeline CLAUDE.md file
openplanr/openplanr · packages/pipeline/CLAUDE.md
git:20260914.622ce31 · audit A · 5 stars
planr-artifact SKILL.md skill
openplanr/openplanr · skills/planr-artifact/SKILL.md · Open, share, import, or export an OpenPlanr diagram, design, or HTML artifact review. Use when feedback must move…
git:20261006.ac4c5c4 · audit A · 5 stars
planr-browser-qa SKILL.md skill
openplanr/openplanr · skills/planr-browser-qa/SKILL.md · Run practical browser-backed QA against real routes, forms, viewports, accessibility, console, and network behavior…
git:20261004.db8c0b9 · audit A · 5 stars

Every file in openplanr/openplanr

Browse by kind, by grade A, or by owner.