multica-requirement-analysis

multica-requirement-analysis is a skill for Claude Code, Codex from it235/multica-best-practices. It costs 32 tokens per session (250 once invoked), scanned A, original, MIT.

A requirement-analysis process that turns a software issue into a clearly defined engineering task. It records the goal, scope, exclusions, constraints, dependencies, testable acceptance criteria, and unanswered questions.

In plain words
What is it for?
Clarifying issue tickets, agreeing on what will and will not change, defining how completion will be tested, and identifying missing information.
Why use it?
It prevents developers or agents from making different guesses about an unclear request. Important ambiguities are surfaced before implementation begins.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Clarifying issue tickets, agreeing on what will and will not change, defining how completion will be tested, and identifying missing information.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/it235/multica-best-practices/multica-requirement-analysis
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add it235/multica-best-practices --skill multica-requirement-analysis
Clone the repo
git clone --depth 1 https://github.com/it235/multica-best-practices

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for multica-requirement-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/it235/multica-best-practices/multica-requirement-analysis/github.svg)](https://agentmods.dev/skills/it235/multica-best-practices/multica-requirement-analysis)
Your own site
<a href="https://agentmods.dev/skills/it235/multica-best-practices/multica-requirement-analysis"><img src="https://agentmods.dev/badge/skills/it235/multica-best-practices/multica-requirement-analysis/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for multica-requirement-analysis

Your own site · 80×15
<a href="https://agentmods.dev/skills/it235/multica-best-practices/multica-requirement-analysis"><img src="https://agentmods.dev/badge/skills/it235/multica-best-practices/multica-requirement-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 250 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.00250
Opus 5 $0.00016 $0.00125
Sonnet 5 $0.00006 $0.00050
Haiku 4.5 $0.00003 $0.00025

Measured 10d ago against content hash b1eda14e4727, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

multica-requirement-analysis scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

templates/en_US/skills/multica-requirement-analysis/SKILL.md · 45 lines

What it actually says

Requirement Analysis

Purpose

Turn an Issue into a clear, actionable engineering task.

Process

  1. Identify the business goal.
  2. Identify the expected behavior.
  3. Identify the explicit scope.
  4. Identify the non-goals.
  5. Identify the constraints.
  6. Identify the acceptance criteria.
  7. Identify ambiguities.
  8. Identify dependencies.

Output

  • Goal: what problem to solve
  • Scope: what will change
  • Non-goals: what explicitly won't change
  • Acceptance criteria: testable check items
  • Constraints: compatibility / performance / security / time
  • Dependencies: prerequisites
  • Open questions: items needing clarification

Rule

Don't silently digest ambiguous requirements.

If an ambiguity would materially affect the implementation:

→ BLOCKED → Ask for clarification.

Why this works

Ambiguity at the requirement stage gets amplified at every later stage. Blocking ambiguity with BLOCKED is far cheaper than letting 5 Agents each guess differently.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 45 lines · 32 tokens per session scan A b1eda14e4727

Subscribe to this mod's changes

multica-requirement-analysis is a skill published in the GitHub repository it235/multica-best-practices (108 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 250 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens