agentmods.dev

implementation-readiness

implementation-readiness is a skill for Codex from HoangNguyen0403/agent-skills-standard. It costs 27 tokens per session (820 once invoked), scanned A, original, MIT.

A readiness-check workflow that verifies product requirements, technical requirements, user-experience details, implementation plans, and tests before coding begins.

In plain words
What is it for?
Use it to review project artifacts, check requirement traceability, and decide whether work can start or must return to planning or design.
Why use it?
It catches missing or unclear decisions early, such as incomplete acceptance criteria, permissions, data changes, failure handling, or performance targets.

Skill for Codex

Written for Codex: installed under .codex/.

not rated 565repo +4 3d ago A scan SkillSpector: pass 27 tokens original MIT

Good fit Use it to review project artifacts, check requirement traceability, and decide whether work can start or must return to planning or design.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hoangnguyen0403/agent-skills-standard/implementation-readiness
View source ↗ HoangNguyen0403/agent-skills-standard npmjs.com
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 HoangNguyen0403/agent-skills-standard --skill implementation-readiness
Clone the repo
git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard

Made for: 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 implementation-readiness

README.md
[![agentmods](https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/implementation-readiness/github.svg)](https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/implementation-readiness)
Your own site
<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/implementation-readiness"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/implementation-readiness/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 implementation-readiness

Your own site · 80×15
<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/implementation-readiness"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/implementation-readiness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 820 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.00027 $0.00820
Opus 5 $0.00014 $0.00410
Sonnet 5 $0.00005 $0.00164
Haiku 4.5 $0.00003 $0.00082

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

Security

Grade A, and why

implementation-readiness 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 9d 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.

.codex/skills/implementation-readiness/SKILL.md · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Implementation Readiness Skill

[!IMPORTANT] Verify BRD-lite, PRD, SRS/FRS, UX, and test prerequisites before implementation starts.

Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, auto_continue=true|false, profile=business|hybrid|technical.

Instructions

When the user asks to perform this workflow, execute the following steps:

Implementation Readiness Workflow

Goal: Decide whether a planned change is ready for implementation or must return to planning/design.

Steps

  1. Load artifacts:

    • BRD-lite brief, PRD/story, SRS/FRS notes, UX/design links, implementation plan, test plan.
    • Jira/GitHub/GitLab/ADO/Figma/Confluence MCP context when configured; otherwise use exported docs or local files.

  2. Check readiness:

    • BRD-lite has business goal, stakeholder, AS-IS to TO-BE, and measurable success metric.
    • ACs atomic, testable, scoped by platform/market/role where relevant.
    • PRD has stable requirement IDs, AC IDs, owner, priority, status, and last-updated note.
    • SRS/FRS identifies touched modules, API/data/interface changes, migrations, permissions, failure modes, and NFR thresholds.
    • Requirement trace is complete: BRD objective -> PRD requirement -> SRS/FRS contract -> test lane.
    • UX/design states cover loading, empty, error, permission, and responsive/mobile cases when UI changes.
    • Test strategy maps ACs to unit, integration, E2E/mobile, security, and Zephyr/manual coverage.
    • Tool prerequisites known: credentials, environments, feature flags, test data, MCP availability.

  3. Decide:

    • READY: BA/PM/SRS/test prerequisites are present and implementation can start.
    • BLOCKED: missing artifact, owner, unclear AC, missing design/architecture, unavailable environment, or unresolved risk.
    • PARTIAL: only named slices can start; blocked slices have explicit owner/input.

  4. Route:

    • For autonomous/channel mode, return READY only with named slices, owners, verification lanes, and available environments.
    • READY -> implement-feature or dev-fix.
    • BLOCKED -> plan-feature or design-solution.
    • PARTIAL -> slice task list plus blockers.

Read the full file on GitHub · 88 lines

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. 9d ago First seen · 88 lines · 27 tokens per session scan A db7a76ac9deb

Subscribe to this mod's changes

implementation-readiness is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 820 once invoked, about $0.0001 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-09-03.

PlanningProject managementReactbest-practicescoding-standardsflutternestjsnextjs
Related

Other skills, from other repositories

intelligence-docs

Keeps the CopilotKit Intelligence landing page in sync when a new Intelligence feature ships or when Intelligence docs are added, renamed, or removed. Use when adding Intelligence capabilities, writing or moving pages under docs/intelligence, editing IntelligenceFeatureCards, or changing…

CopilotKit/CopilotKit · 83 tokens

plan

PM planning workflow that gathers requirements, decomposes them into prioritized tasks, defines API contracts, and produces both a machine-readable plan and a human-readable tracker in docs/plans/.

first-fluke/fullstack-starter · 37 tokens

coordinate-pro

Thorough version of coordinate - high-quality development workflow with 11 review steps out of 17.

first-fluke/fullstack-starter · 22 tokens

coordinate

Coordinate multiple agents for a complex multi-domain project using PM planning, parallel agent spawning, and QA review.

first-fluke/fullstack-starter · 22 tokens

exec-plan

Create, manage, and track execution plans as first-class repository artifacts in docs/exec-plans/.

first-fluke/fullstack-starter · 23 tokens

work

Coordinate multiple agents for a complex multi-domain project using PM planning, parallel agent spawning, and QA review.

first-fluke/fullstack-starter · 22 tokens