New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Mcaf Feature Spec

by managedcode in managedcode/Storage

Create or update a feature spec under docs/Features/ with business rules, user flows, system behaviour, verification, and Definition of Done.

MITAuto-check passedProduct & Project Management

Install Mcaf Feature Spec

skills CLI
$ npx skills add managedcode/Storage --skill mcaf-feature-spec -a claude-code

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

GitHub CLI
$ gh skill install managedcode/Storage mcaf-feature-spec --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/managedcode/Storage.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/mcaf-feature-spec .claude/skills/mcaf-feature-spec && 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
mcaf-feature-spec
GitHub stars
138
Token cost
~959 tokens
SKILL.md length
451 words
Files
2 (incl. references)
Skills in repo
41
Repo updated
First seen
Licence
MIT

At a glance

Create or update a feature spec under docs/Features/ with business rules, user flows, system behaviour, verification, and Definition of Done.

  • Works in 3 steps: Read the nearest AGENTS.md and confirm… → Run this skill's Workflow through the… → Return the Required Result Format with…
  • The user asks for a feature spec
  • SKILL.md covers Trigger On, Value, Do Not Use For and Inputs, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Mcaf Feature Spec is an agent skill from managedcode/Storage. Create or update a feature spec under docs/Features/ with business rules, user flows, system behaviour, verification, and Definition of Done. Use when the user asks for a feature spec, executable requirements, acceptance criteria, behaviour documentation, or a pre-implementation plan for non-trivial behaviour changes.

Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/feature-template.md`). Compatibility notes: Requires repository write access; produces Markdown docs with Mermaid diagrams and executable verification steps.

It sits in Product & Project Management, covering PRD writing, UX design and Planning. The repository describes itself as: Storage library provides a universal interface for accessing and manipulating data in different cloud blob storage providers. The licence is MIT.

When your agent uses it

  • The user asks for a feature spec
  • Executable requirements
  • Acceptance criteria
  • Behaviour documentation

Example prompts

  • “/mcaf-feature-spec”

Requirements

  • Compatibility (from SKILL.md): Requires repository write access; produces Markdown docs with Mermaid diagrams and executable verification steps.

Workflow steps

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

  1. Read the nearest AGENTS.md and confirm scope and constraints.
  2. Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
  3. Return the Required Result Format with concrete artifacts and verification evidence.

What it can do on your machine

Read from SKILL.md and the folder at commit 5d32121. 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

    No scripts in the folder and no shell commands in SKILL.md.

    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.

  • Compatibility

    Requires repository write access; produces Markdown docs with Mermaid diagrams and executable verification steps.

    From compatibility in the SKILL.md frontmatter.

Context cost

Mcaf Feature Spec loads about 959 tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 85 tokens; SKILL.md has 451 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~85
When it runs · the whole SKILL.md, loaded when a task matches
~959
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.3k

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from managedcode/Storage at commit 5d32121, republished under its MIT licence (© managedcode). 451 words, ~959 tokens.

Download SKILL.mdSave it as .claude/skills/mcaf-feature-spec/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
mcaf-feature-spec
description
Create or update a feature spec under `docs/Features/` with business rules, user flows, system behaviour, verification, and Definition of Done. Use when the user asks for a feature spec, executable requirements, acceptance criteria, behaviour documentation, or a pre-implementation plan for non-trivial behaviour changes.
compatibility
Requires repository write access; produces Markdown docs with Mermaid diagrams and executable verification steps.

MCAF: Feature Spec

Trigger On

  • add or change non-trivial behaviour
  • behaviour is under-specified and engineers are guessing
  • tests need a stable behavioural source of truth

Value

  • produce a concrete project delta: code, docs, config, tests, CI, or review artifact
  • reduce ambiguity through explicit planning, verification, and final validation skills
  • leave reusable project context so future tasks are faster and safer

Do Not Use For

  • architecture decisions that need alternatives and trade-offs
  • tiny typo or cosmetic-only changes with no behavioural impact

Inputs

  • docs/Architecture.md
  • the nearest AGENTS.md
  • current user flows, business rules, and acceptance expectations

Quick Start

  1. Read the nearest AGENTS.md and confirm scope and constraints.
  2. Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
  3. Return the Required Result Format with concrete artifacts and verification evidence.

Workflow

  1. Define scope first: in scope, out of scope, boundaries touched.
  2. If the feature doc is missing, scaffold from references/feature-template.md.
  3. Keep the spec executable:
    • numbered rules
    • main flow
    • edge and failure flows
    • system behaviour
    • verification steps
    • Definition of Done
  4. Make the spec concrete enough that tests can be written without guessing.
  5. If the feature creates a new dependency, boundary, or major policy shift, update an ADR too.

Deliver

  • docs/Features/feature-name.md
  • a feature spec that engineers and agents can implement directly

Validate

  • rules are testable, not aspirational
  • edge cases are captured where they matter
  • verification steps match the intended behaviour
  • the doc can drive implementation without hidden tribal knowledge
Show full SKILL.md (209 more words)Show less

Ralph Loop

Use the Ralph Loop for every task, including docs, architecture, testing, and tooling work.

  1. Plan first (mandatory):
    • analyze current state
    • define target outcome, constraints, and risks
    • write a detailed execution plan
    • list final validation skills to run at the end, with order and reason
  2. Execute one planned step and produce a concrete delta.
  3. Review the result and capture findings with actionable next fixes.
  4. Apply fixes in small batches and rerun the relevant checks or review steps.
  5. Update the plan after each iteration.
  6. Repeat until outcomes are acceptable or only explicit exceptions remain.
  7. If a dependency is missing, bootstrap it or return status: not_applicable with explicit reason and fallback path.
Required Result Format
  • status: complete | clean | improved | configured | not_applicable | blocked
  • plan: concise plan and current iteration step
  • actions_taken: concrete changes made
  • validation_skills: final skills run, or skipped with reasons
  • verification: commands, checks, or review evidence summary
  • remaining: top unresolved items or none

For setup-only requests with no execution, return status: configured and exact next commands.

Load References

  • use references/feature-template.md only for scaffolding

Example Requests

  • "Write a feature spec for the new checkout retry flow."
  • "Document the behaviour before coding this API change."
  • "Turn this loose requirement into an executable feature doc."

© managedcode, 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 (references) in .codex/skills/mcaf-feature-spec of managedcode/Storage.

  • SKILL.md
  • references/feature-template.md

Open the folder on GitHubat commit 5d32121

Compare with similar skills

Mcaf Feature Spec 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.

Mcaf Feature Spec compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Mcaf Feature Spec this skillmanagedcode/Storage138—~959Automated safety check: PassMIT
AlignmentOvid/paad131—~4.9kAutomated safety check: PassMIT
Clarification AnalystGulajavaMinistudio/Mayukai-Theme139—~1.1kAutomated safety check: PassMIT
Feature SpecPackmindHub/packmind317—~1.8kAutomated safety check: PassApache-2.0
Run Judgesclosedloop-ai/claude-plugins122—~15kAutomated safety check: NotesApache-2.0
Dex Improvedavekilleen/Dex493—~2.8kAutomated safety check: PassCustom licence

Similar skills

  • 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 today
    Product & Project ManagementAuto-check passed

  • Clarification Analyst

    GulajavaMinistudio/Mayukai-Theme

    Helps interrogate Product Requirements (PRD), Technical Specifications, and Implementation Plans to find ambiguities, missing edge cases, and hidden assumptions.

    139 GitHub stars~1.1k tokensUpdated 3 mo ago
    Product & Project ManagementAuto-check passed

  • Feature Spec

    PackmindHub/packmind

    Generate a Packmind feature specification from a GitHub issue, file, URL, or direct description.

    317 GitHub stars~1.8k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Run Judges

    closedloop-ai/claude-plugins

    Orchestrate parallel judge agent execution, aggregate CaseScore results, write plan-judges.json, code-judges.json, prd-judges.json, or feature-judges.json, and validate output.

    122 GitHub stars~15k tokensUpdated today
    Product & Project ManagementAuto-check: notes

  • Dex Improve

    davekilleen/Dex

    Workshop one improvement idea into an implementation plan. An agent skill from davekilleen/Dex.

    493 GitHub stars~2.8k tokensUpdated 5 days ago
    Product & Project ManagementAuto-check passed

  • Prd To Plan

    Dwlad90/stylex-swc-plugin

    Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/.

    111 GitHub stars~767 tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed

More from managedcode/Storage

All 41 skills in this repo

  • Mcaf Adr Writing

    managedcode/Storage

    Create or update an ADR under docs/ADR/ for architectural decisions, dependency changes, data-model changes, or cross-cutting policy shifts.

    138 GitHub stars~951 tokensUpdated yesterday
    Auto-check passed

  • Mcaf Agile Delivery

    managedcode/Storage

    Shape delivery workflow around backlog quality, roles, ceremonies, and engineering feedback.

    138 GitHub stars~883 tokensUpdated yesterday
    Auto-check passed

  • Mcaf Architecture Overview

    managedcode/Storage

    Create or update docs/Architecture.md as the global architecture map for a solution.

    138 GitHub stars~950 tokensUpdated yesterday
    Auto-check passed

  • Mcaf CI CD

    managedcode/Storage

    Design or refine CI/CD workflows, quality gates, release flow, and safe AI-assisted pipeline authoring.

    138 GitHub stars~981 tokensUpdated yesterday
    Auto-check passed

  • Mcaf Code Review

    managedcode/Storage

    Prepare for, perform, or tighten code review workflow: PR scope, review checklist, reviewer expectations, and merge hygiene.

    138 GitHub stars~957 tokensUpdated yesterday
    Auto-check passed

  • Mcaf Devex

    managedcode/Storage

    Improve developer experience for multi-component solutions: onboarding, F5 contract, cross-platform tasks, local inner loop, and reproducible setup.

    138 GitHub stars~911 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Mcaf Feature Spec

What does Mcaf Feature Spec do?

Create or update a feature spec under docs/Features/ with business rules, user flows, system behaviour, verification, and Definition of Done. Mcaf Feature Spec is an agent skill from managedcode/Storage. Create or update a feature spec under docs/Features/ with business rules, user flows, system behaviour, verification, and Definition of Done.

When should I use Mcaf Feature Spec?

Mcaf Feature Spec fits situations like: the user asks for a feature spec; executable requirements; acceptance criteria; behaviour documentation.

How do I install Mcaf Feature Spec in Claude Code?

Run `npx skills add managedcode/Storage --skill mcaf-feature-spec -a claude-code`. Or copy the skill folder (.codex/skills/mcaf-feature-spec in managedcode/Storage) into .claude/skills/mcaf-feature-spec in your project. Claude Code loads it when a task matches its description.

How do I install Mcaf Feature Spec in Codex?

Run `npx skills add managedcode/Storage --skill mcaf-feature-spec -a codex`. Or copy the skill folder (.codex/skills/mcaf-feature-spec in managedcode/Storage) into .agents/skills/mcaf-feature-spec in your project. Codex loads it when a task matches its description.

Can I use Mcaf Feature Spec 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 managedcode/Storage --skill mcaf-feature-spec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mcaf-feature-spec, .gemini/skills/mcaf-feature-spec, .github/skills/mcaf-feature-spec and .opencode/skills/mcaf-feature-spec in your project.

What does Mcaf Feature Spec need to run?

SKILL.md names no scripts, command-line tools or credentials: Mcaf Feature Spec is instructions for the agent only. Compatibility (from SKILL.md): Requires repository write access; produces Markdown docs with Mermaid diagrams and executable verification steps..

Does Mcaf Feature Spec 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 Mcaf Feature Spec 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. Review the folder before installing.

What licence does Mcaf Feature Spec use?

Mcaf Feature Spec 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 Mcaf Feature Spec use?

About 959 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.4k tokens, read only when the agent opens those files.

What are the alternatives to Mcaf Feature Spec?

Skills that share tags, products or a category with Mcaf Feature Spec: Alignment (Ovid/paad, 131 stars), Clarification Analyst (GulajavaMinistudio/Mayukai-Theme, 139 stars), Feature Spec (PackmindHub/packmind, 317 stars) and Run Judges (closedloop-ai/claude-plugins, 122 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Mcaf Feature Spec?

managedcode (a GitHub organization) maintains it in managedcode/Storage, which has 138 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on October 7, 2026.

Source: managedcode/Storage on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.