Agent skill

Workflow Status

by nurettincoban in nurettincoban/ai-prd-workflow

Report which workflow artifacts exist, which RFCs are implemented and reviewed, what has drifted, and the next step.

MITAuto-check passedProduct & Project Management

Install Workflow Status

skills CLI
$ npx skills add nurettincoban/ai-prd-workflow --skill workflow-status -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install nurettincoban/ai-prd-workflow workflow-status --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/nurettincoban/ai-prd-workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/workflow-status .claude/skills/workflow-status && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
workflow-status
GitHub stars
298
Token cost
~994 tokens
SKILL.md length
437 words
Files
2 (incl. scripts)
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Report which workflow artifacts exist, which RFCs are implemented and reviewed, what has drifted, and the next step.

  • Works in 5 steps: Which artifacts exist: PRD.md,… → Which RFCs are implemented? Start from… → Which RFCs have been reviewed? Check… → …
  • Tasks that involve PRD writing
  • Runs Python scripts from its folder; calls python3

What it does

Workflow Status is an agent skill from nurettincoban/ai-prd-workflow. Report which workflow artifacts exist, which RFCs are implemented and reviewed, what has drifted, and the next step.

Its SKILL.md is about 990 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/trace-check.py`).

It sits in Product & Project Management, covering PRD writing. The repository describes itself as: RFC-driven development for AI coding agents: idea or existing codebase → verified PRD → features → rules → sequenced RFCs → reviewed code. Agent Skills for Claude Code, Codex… The licence is MIT.

When your agent uses it

  • Tasks that involve PRD writing

Example prompts

  • “/workflow-status”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Which artifacts exist: PRD.md, PRD-REVIEW.md, FEATURES.md, RULES.md, RFCS.md, RFCs/ folder, TEST-STRATEGY.md, reviews/, changes/?
  2. Which RFCs are implemented? Start from the Status column in RFCS.md, which /implement-rfc and /review-rfc keep current, then verify it…
  3. Which RFCs have been reviewed? Check reviews/ for a report per implemented RFC — an implemented RFC with no review is the most common…
  4. Are there open change requests in changes/ whose decisions are still pending?
  5. Any signs of drift: code that contradicts the PRD or RULES.md, features in the codebase with no RFC, an RFC implemented before its…

What it can do on your machine

Read from SKILL.md and the folder at commit b67f4d3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Workflow Status loads about 994 tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 437 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~33
When it runs · the whole SKILL.md, loaded when a task matches
~994

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from nurettincoban/ai-prd-workflow at commit b67f4d3, republished under its MIT licence (© nurettincoban). 437 words, ~994 tokens.

Download SKILL.mdSave it as .claude/skills/workflow-status/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
workflow-status
description
Report which workflow artifacts exist, which RFCs are implemented and reviewed, what has drifted, and the next step.
metadata.source
https://github.com/nurettincoban/ai-prd-workflow
metadata.version
3.0.0
metadata.checksum
sha256:9088401f342f4a6e031009e15fff062c2e6385de834fc7a63c1d33b2fc602094

You are guiding a project through an RFC-driven development workflow with these stages:

#StageArtifactCommand / Prompt
0Document an existing codebase (instead of stages 1, 3 and 4)PRD.md, FEATURES.md, RULES.md/document-existing (document-existing-prompt.md)
1Create PRDPRD.md/create-prd (interactive-prd-creation-prompt.md)
2Verify PRDPRD.md (improved) + PRD-REVIEW.md/verify-prd (prd-comprehensive-verification-prompt.md)
3Extract featuresFEATURES.md/extract-features (prd-to-features-prompt.md)
4Generate rulesRULES.md/generate-rules (prd-to-rules-prompt.md)
5Generate RFCsRFCs/ folder + RFCS.md/generate-rfcs (prd-to-rfcs-prompt.md)
6Testing strategyTEST-STRATEGY.md/test-strategy (testing-strategy-prompt.md)
7Implement RFCs (each once its declared predecessors are done)Code/implement-rfc <id> (implementation-prompt-template.md)
8Review each implementationreviews/REVIEW-RFC-<id>.md/review-rfc <id> (code-review-prompt.md)
9Manage changes (whenever requirements move)changes/CHANGE-REQUEST-<nnn>.md/manage-changes (prd-change-management-prompt.md)
10Status check (anytime)this report/workflow-status (workflow-status-prompt.md)

Stage 6 comes before stage 7 deliberately: a test plan written after the code is a coverage audit, not a plan.

Inspect the current project to determine workflow progress. If trace-check.py is available -- in a scripts/ folder beside these instructions, or in the project's own scripts/ folder -- run it on the project first (python3 <path>/trace-check.py .): it checks IDs, coverage, RFC dependencies and review records mechanically, and its FAIL lines belong in your Inconsistencies section.

  1. Which artifacts exist: PRD.md, PRD-REVIEW.md, FEATURES.md, RULES.md, RFCS.md, RFCs/ folder, TEST-STRATEGY.md, reviews/, changes/?
  2. Which RFCs are implemented? Start from the Status column in RFCS.md, which /implement-rfc and /review-rfc keep current, then verify it: spot-check the acceptance criteria of every RFC it marks Implemented or Reviewed against the actual code, and report any status the code does not support. Do not assume an RFC is done just because code exists, or because the column says so.
  3. Which RFCs have been reviewed? Check reviews/ for a report per implemented RFC — an implemented RFC with no review is the most common real-world gap, and reviews are exactly what gets skipped under deadline.
  4. Are there open change requests in changes/ whose decisions are still pending?
  5. Any signs of drift: code that contradicts the PRD or RULES.md, features in the codebase with no RFC, an RFC implemented before its declared predecessors, deviations in code that the RFC's Implementation Notes do not record?
Show full SKILL.md (97 more words)Show less

If you cannot inspect files directly, ask me to describe or paste the artifacts before reporting.

Then report:

  1. Status table — each workflow stage with its artifact and status (Done / In progress / Missing / Stale)

  2. Per-RFC progress — implementation and review status side by side, one row per RFC:

    RFC-001  implemented ✅   reviewed ❌
    RFC-002  implemented ✅   reviewed ❌
    RFC-003  implemented ✅   reviewed ✅

    A single "reviews done" row hides which RFCs were actually reviewed. Report them individually.

  3. Inconsistencies — anything drifted, skipped, or contradictory, with file references

  4. Next step — the single recommended next action, with the exact command or prompt to run

© nurettincoban, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (scripts) in skills/workflow-status of nurettincoban/ai-prd-workflow.

  • SKILL.md
  • scripts/trace-check.py

Open the folder on GitHubat commit b67f4d3

Compare with similar skills

Workflow Status next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Workflow Status compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Workflow Status this skillnurettincoban/ai-prd-workflow298—~994Automated safety check: PassMIT
Schematicblader/schematic240—~2.2kAutomated safety check: PassMIT
Vscuse Scenario AuthoringOfficeDev/microsoft-365-agents-toolkit781—~4.3kAutomated safety check: PassCustom licence
AlignmentOvid/paad131—~4.9kAutomated safety check: PassMIT
Write A Specinkeep/open-knowledge4.4k—~4.9kAutomated safety check: PassGPL-3.0
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT

Similar skills

  • Schematic

    blader/schematic

    Reverse engineer a detailed product and technical specification document from a git branch's implementation.

    240 GitHub stars~2.2k tokensUpdated 7 mo ago
    Product & Project ManagementAuto-check passed
  • Vscuse Scenario Authoring

    OfficeDev/microsoft-365-agents-toolkit

    A skill your agent uses when: reading a docs scenario, PRD, mockup, or user flow and using vscuse-ui/noVNC as the primary authoring surface to record, generate, replace, or update vscuse test plans…

    781 GitHub stars~4.3k tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Alignment

    Ovid/paad

    A skill your agent uses when verifying that requirements/specs/PRDs and their implementation plans match — before starting work, after a spec or plan update, or when suspecting coverage gaps, scope…

    131 GitHub stars~4.9k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed
  • Write A Spec

    inkeep/open-knowledge

    Scope a feature end to end and write an implementation spec under specs/ from an accepted proposal — current-system mapping, goals/non-goals, a Decision Log for one-way-door choices, a live Open…

    4.4k GitHub stars~4.9k tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed
  • Ralph Tui Create Beads

    subsy/ralph-tui

    Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.

    2.5k GitHub starsUsed in 1 repo~2.6k tokens
    Product & Project ManagementAuto-check passed

More from nurettincoban/ai-prd-workflow

All 11 skills in this repo
  • Generate Rfcs

    nurettincoban/ai-prd-workflow

    Break the PRD into sequenced implementation RFCs under RFCs/ with an RFCS.md index, then cold-read each RFC for gaps.

    298 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed
  • Document Existing

    nurettincoban/ai-prd-workflow

    Document an existing codebase as PRD.md, FEATURES.md and RULES.md, so new work is planned against the code as it is.

    298 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed
  • Generate Rules

    nurettincoban/ai-prd-workflow

    Write RULES.md, the project standards the AI must follow, with registry-verified dependency versions and permanent rule IDs.

    298 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed
  • Test Strategy

    nurettincoban/ai-prd-workflow

    Write TEST-STRATEGY.md, a test plan per RFC, before the tests are written.

    298 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed
  • Verify Prd

    nurettincoban/ai-prd-workflow

    Review PRD.md for gaps, contradictions and unverifiable claims, write an improved PRD.md and record the findings in PRD-REVIEW.md.

    298 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Extract Features

    nurettincoban/ai-prd-workflow

    Turn PRD.md into FEATURES.md: permanent feature IDs, MoSCoW priorities, acceptance criteria and the PRD requirement each feature comes from.

    298 GitHub stars~1k tokensUpdated yesterday
    Auto-check passed

Questions about Workflow Status

What does Workflow Status do?

Report which workflow artifacts exist, which RFCs are implemented and reviewed, what has drifted, and the next step. Workflow Status is an agent skill from nurettincoban/ai-prd-workflow. Report which workflow artifacts exist, which RFCs are implemented and reviewed, what has drifted, and the next step.

When should I use Workflow Status?

Workflow Status fits situations like: tasks that involve PRD writing.

How do I install Workflow Status in Claude Code?

Run `npx skills add nurettincoban/ai-prd-workflow --skill workflow-status -a claude-code`. Or copy the skill folder (skills/workflow-status in nurettincoban/ai-prd-workflow) into .claude/skills/workflow-status in your project. Claude Code loads it when a task matches its description.

How do I install Workflow Status in Codex?

Run `npx skills add nurettincoban/ai-prd-workflow --skill workflow-status -a codex`. Or copy the skill folder (skills/workflow-status in nurettincoban/ai-prd-workflow) into .agents/skills/workflow-status in your project. Codex loads it when a task matches its description.

Can I use Workflow Status in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nurettincoban/ai-prd-workflow --skill workflow-status -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workflow-status, .gemini/skills/workflow-status, .github/skills/workflow-status and .opencode/skills/workflow-status in your project.

What does Workflow Status need to run?

Going by SKILL.md and its folder, Workflow Status needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Workflow Status access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Workflow Status safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Workflow Status use?

Workflow Status is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Workflow Status use?

About 994 tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Workflow Status?

Skills that share tags, products or a category with Workflow Status: Schematic (blader/schematic, 240 stars), Vscuse Scenario Authoring (OfficeDev/microsoft-365-agents-toolkit, 781 stars), Alignment (Ovid/paad, 131 stars) and Write A Spec (inkeep/open-knowledge, 4.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Workflow Status?

nurettincoban (a GitHub user) maintains it in nurettincoban/ai-prd-workflow, which has 298 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 8, 2026.

Source: nurettincoban/ai-prd-workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.