Run any Skill in Manus with one click

Get Started

implementation-readiness

Stars11

Forks2

UpdatedJune 15, 2026 at 04:55

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

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

gabrielmoreira

gabrielmoreira/agent-skills-mirror

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

SKILL.md

readonly

name	implementation-readiness
description	Verify BRD-lite, PRD, SRS/FRS, UX, and test prerequisites before implementation starts.
metadata	{"triggers":{"keywords":["implementation readiness","workflow"]}}

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.

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

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.
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.
Decide:
- READY: implementation can start.
- BLOCKED: missing artifact, unclear AC, missing design/architecture, unavailable environment, or unresolved risk.
- PARTIAL: implementation may start only for named slices with blocked slices isolated.
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.

Output Template

# Implementation Readiness

## Verdict

## Ready Slices

## Blocking Gaps

| Area | Gap | Owner/Input Needed |
| --- | --- | --- |
| [area] | [gap] | [owner/input] |

## Runtime Contract

## Handoff Payload

## Blocking Questions

## Next Workflow

## Cost Report
Call `get_session_cost(workflow="implementation-readiness")` before final handoff.

More from this repository

same repository

executing-plans

gabrielmoreira/agent-skills-mirror

Use when you have a written implementation plan to execute in a separate session with review checkpoints

2026-07-0411

verification-before-completion

gabrielmoreira/agent-skills-mirror

Use when about to claim work is complete, fixed, passing, verified, release-ready, or ready to commit, merge, publish, or hand off.

2026-07-0411

claw-orchestrator

gabrielmoreira/agent-skills-mirror

Manage persistent coding sessions across Claude Code, Codex, Gemini, Cursor, and OpenCode engines. Use when orchestrating multi-engine coding agents, starting/sending/stopping sessions, running multi-agent council collaborations, cross-session messaging, ultraplan deep planning, ultrareview parallel code review, autoloop autonomous workspace iteration, ultraapp building deployable web apps from a structured Q&A interview, switching models/tools at runtime, or exposing the orchestrator's 65 tools as an MCP server to Hermes Agent / Claude Desktop / Cursor / Cline / Continue / Zed / Windsurf / Goose. Triggers on "start a session", "send to session", "run council", "ultraplan", "ultrareview", "autoloop", "ultraapp", "Forge tab", "build a web app", "one-click app", "AppSpec", "autonomous iteration", "iterate until goal", "deep paper review", "auto research", "switch model", "multi-agent", "coding session", "session inbox", "cursor agent", "opencode", "mcp server", "clawo-mcp", "hermes mcp", "model context protocol

2026-07-0311

using-aegis

gabrielmoreira/agent-skills-mirror

Use when starting a turn or checking Aegis skill routing.

2026-07-0311

baoyu-wechat-summary

gabrielmoreira/agent-skills-mirror

Summarizes WeChat group chat highlights into a structured digest using the local wx-cli binary (https://github.com/jackwener/wx-cli). Generates a normal digest by default; a roast (毒舌) version is opt-in. Maintains per-group history (history.json + history-digests.jsonl), per-user profiles, and per-group fact memory (memory.md) across runs, with privacy guardrails baked in. Use when the user asks to "总结群聊", "群聊精华", "群聊摘要", "summarize group chat", "group chat digest", mentions a WeChat group name with a time range, says "帮我看看 XX 群最近聊了什么", "XX 群有什么值得看的", or asks to "回溯画像" / "初始化画像" / "backfill profiles". Adds the roast version when the user says "毒舌版", "roast 版", "再来个毒舌的", or similar.

2026-07-0311

systematic-debugging

gabrielmoreira/agent-skills-mirror

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

2026-07-0211

Implementation Readiness Workflow

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

Steps

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.

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.

Decide:

READY: implementation can start.
BLOCKED: missing artifact, unclear AC, missing design/architecture, unavailable environment, or unresolved risk.
PARTIAL: implementation may start only for named slices with blocked slices isolated.

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.

Output Template

# Implementation Readiness ## Verdict ## Ready Slices ## Blocking Gaps | Area | Gap | Owner/Input Needed | | --- | --- | --- | | [area] | [gap] | [owner/input] | ## Runtime Contract ## Handoff Payload ## Blocking Questions ## Next Workflow ## Cost Report Call `get_session_cost(workflow="implementation-readiness")` before final handoff.