plan-requirements SKILL.md skillA

plan-requirements from foyzulkarim/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add foyzulkarim/skills/plan-requirements@git:20260724.cdb1a53

Pins git:20260724.cdb1a53 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
foyzulkarim/skills
Path
dev-pipeline/skills/plan-requirements/SKILL.md
Versions recorded
5
Latest version
git:20260724.cdb1a53, committed Jul 24, 2026
First version recorded
May 1, 2026
Size
10,787 bytes
Repository stars
43
License
none declared

Phase 1 of 5 — Socratic interview capturing WHAT and WHY; outputs a sprint-sized REQ doc for plan-architecture. Use only when the user asks to run Phase 1, plan requirements, or start the requirements interview — never trigger automatically from a feature description.

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

# Plan-Requirements Skill

You are a senior product-minded interviewer running **Phase 1 of 5: Requirement Engineering**. Interview the user — typically a PM, team lead, or developer wearing the PM hat — to capture **what we're building and why**, then produce a requirements document (`/specs/requirements/REQ-<N>-<slug>.md` — see **Output Naming** below) that feeds the plan-architecture skill (Phase 2).

Three principles govern everything below:

1. **Audience: the whole team, cold.** The REQ is what a PM hands to the team before sprint planning. Any teammate — IC, QA, lead — who was *not* in this conversation must be able to read it end-to-end and walk into sprint planning with full context.
2. **Sprint-sized.** One REQ = one chunk the team can commit to in a single sprint. If the conversation reveals more, help the user split into multiple REQs *here* — each slice independently demonstrable — rather than pushing the problem downstream.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add foyzulkarim/skills/plan-requirements@sha256:d123b565832708be

The line at the top of this page pins the label git:20260724.cdb1a53, 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_7z6j3agei47d64rt.svg)](https://markdownregistry.com/a/art_7z6j3agei47d64rt)

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

Versions

The registry has recorded 5 versions of this file, between May 1, 2026 and Jul 24, 2026, about one every 21 days.

versioncommittedcommitsizeaudit
git:20260724.cdb1a53 latest2026-07-24 cdb1a53 10,787 BA view · diff
git:20260723.6a602de2026-07-23 6a602de 9,506 BA view · diff
git:20260705.72cac2a2026-07-05 72cac2a 9,717 BA view · diff
git:20260509.1888cd32026-05-09 1888cd3 18,846 BA view · diff
git:20260501.26931102026-05-01 2693110 18,528 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 (10787 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

foyzulkarim/skills · 43 stars · license none declared · pushed 2026-09-04 · branch master

API

GET https://markdownregistry.com/api/v1/artifacts/art_7z6j3agei47d64rt
GET https://markdownregistry.com/api/v1/resolve?ref=foyzulkarim/skills/plan-requirements
GET https://markdownregistry.com/api/v1/blob/d123b565832708be7dec4fea82ac8c3ff7ee29a59ad69cd12c840d9f380e5d57

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 foyzulkarim/skills

AGENTS.md AGENTS.md file
foyzulkarim/skills · AGENTS.md
git:20260904.8f83398 · audit B · 43 stars
CLAUDE.md CLAUDE.md file
foyzulkarim/skills · CLAUDE.md
git:20260831.b6940c2 · audit A · 43 stars
archive-issue SKILL.md skill
foyzulkarim/skills · dev-pipeline/skills/archive-issue/SKILL.md · Retire a closed issue's working artifacts out of specs/ into the GitHub wiki. Use only when the user asks to archive a…
git:20260823.71acb2d · audit A · 43 stars
commit SKILL.md skill
foyzulkarim/skills · dev-pipeline/skills/commit/SKILL.md · One-shot conventional commit; bundled scripts adaptively gather diff context, draft the message, and stage+commit —…
git:20260724.cdb1a53 · audit A · 43 stars
execute-qa SKILL.md skill
foyzulkarim/skills · dev-pipeline/skills/execute-qa/SKILL.md · Executes a QA specification (specs/qa/QA-<N>-<slug>.md) written by /plan-qa: drives every step with the plan's drivers…
git:20260831.b6940c2 · audit A · 43 stars
finish-worktree SKILL.md skill
foyzulkarim/skills · dev-pipeline/skills/finish-worktree/SKILL.md · After an issue's PR has squash-merged on GitHub and its issue has closed: fast-forward the default branch, remove the…
git:20260724.cdb1a53 · audit A · 43 stars
generate-tasks SKILL.md skill
foyzulkarim/skills · dev-pipeline/skills/generate-tasks/SKILL.md · Phase 3 of 5 — slices the ARCH doc into verification-ready task specs (tdd/test-after/ui/checklist), emitted as a…
git:20260823.71acb2d · audit A · 43 stars
implement SKILL.md skill
foyzulkarim/skills · dev-pipeline/skills/implement/SKILL.md · Phase 4 of 5 — implements tasks from TASKS-<N>-<slug>.md (with ARCH-<N>-<slug>.md as architecture-only context) using…
git:20260823.71acb2d · audit A · 43 stars
move-to-worktree SKILL.md skill
foyzulkarim/skills · dev-pipeline/skills/move-to-worktree/SKILL.md · After /start-task: park the current clean, pushed feature branch in its own issue-numbered nested worktree…
git:20260823.71acb2d · audit A · 43 stars
plan-architecture SKILL.md skill
foyzulkarim/skills · dev-pipeline/skills/plan-architecture/SKILL.md · Phase 2 of 5 — collaborative system design plus change-footprint mapping; outputs an ARCH doc for generate-tasks. Use…
git:20260823.71acb2d · audit A · 43 stars
plan-qa SKILL.md skill
foyzulkarim/skills · dev-pipeline/skills/plan-qa/SKILL.md · Post-implementation QA planning — independent of /review (the developer chooses whether to run them sequentially or in…
git:20260831.b6940c2 · audit A · 43 stars
release-notes SKILL.md skill
foyzulkarim/skills · dev-pipeline/skills/release-notes/SKILL.md · Draft a changelog for the next release by summarizing git commits since the last tag. Use only when the user asks to…
git:20260724.cdb1a53 · audit A · 43 stars

Every file in foyzulkarim/skills

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