--- name: implementation-readiness-2e499b69db49 description: "Verify BRD-lite, PRD, SRS/FRS, UX, and test prerequisites before implementation starts." metadata: internal: true 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=, 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: - Load task-linked approved brief/ticket, PRD/story or equivalent approved evidence, canonical ledger (`docs/product//evidence.json`) when present, SRS/FRS when needed, UX/design evidence, implementation plan, and test plan. - Do not require a separate filename when an approved task record supplies the necessary information; missing documents do not force repeat intake. A matching record and stable slug are required; unrelated documents/working-tree changes are not authority or approval. 2. Check readiness: - Approved task record supplies outcome, constraints/non-goals, testable ACs, owner and approval; equivalent approved low-risk evidence suffices without separate BRD/PRD/SRS files. `approval: approved` passes; `pending` blocks; `assumed-autonomous` warns and blocks only when `snc_tier=high`. Sensitive trust-boundary changes still require applicable design/human floor. - ACs have one observable behavior per AC across happy, edge, and error paths, with necessary preconditions and platform/market/role scope; truth tables for interacting conditions. Examine scope coverage and conflicts before issuing READY or PARTIAL; consequential conflicts block affected slices with consequence, owner, and required input without inventing business/error policy. - Affected-scope evidence freshness and current authority: stale or disputed decisions block only the consuming action, never a global block on independent approved scope. - Human risk acceptance: where lawful, an explicit recorded release `risk_accept` decision documents uncertainty and rationale; it waives specific baseline sources for release only, but never converts unvalidated/inconclusive evidence into validated proof, and cannot authenticate host approval. An investment `risk_accept` documents uncertainty and rationale without waiving evidence or altering product state. Missing monetary data is not a qualitative-investment blocker. - Optional product capability gap: if optional product-evidence capability (`product-evidence` / `product-management` package / script / Node >=20) is absent, record exact gap in `missing_evidence` (e.g. `Capability gap: not installed; opt in at a reviewed ref and sync`), preserve `feature_status`, and treat product gate result as an unvalidated proposal only; other missing required tooling or environment remains a BLOCKED prerequisite for the affected slice. - Available requirement/design evidence identifies affected modules and consequential API/data/interface/migration/permission/failure/NFR choices; unresolved sensitive or consequential choices route to technical design and human approval. - Requirement trace links business/product requirements to technical contracts and test lanes; review affected contracts, ACs, approvals and evidence for change impact without restarting unchanged decisions or inventing document detours. - Apply the shared requirements-modeling distinctions for material conflicts, requirement quality versus need evidence, and applicable temporary transition needs; assess only affected slices. When readiness relies on elicited stakeholder meaning, consult the BRD confirmation procedure directly without routing through brainstorm/full BRD. - UX/design evidence covers loading, empty, error, permission, responsive/mobile cases when UI changes. - Test strategy maps ACs to available unit, integration, E2E/mobile, security, Zephyr/manual lanes; record unavailable optional lanes as blockers on only affected slices. - Tool prerequisites known: credentials, environments, feature flags, test data, MCP availability. Schedulable delivery dependencies required; legitimate business or state loops are not delivery-dependency cycles, but unresolved behavioral, permission, environment, or scheduling prerequisites block affected slices. 3. Decide: - READY: approved evidence, owner, ACs, required design/approval and test prerequisites permit named slice(s) to start. - BLOCKED: required authority/approval, owner, unclear AC, consequential design, environment, or risk unresolved; do not recommend unconditional implementation. - PARTIAL: name each independently bounded ready slice with owner, approval and verification lane; name each blocked slice with its owner, dependency/input and reason. Only ready slices may flow downstream. 4. Route: - For autonomous/channel mode, return READY only with named slices, owners, verification lanes, approval and available required environments. - READY -> `implement-feature` or `dev-fix`. - BLOCKED -> `plan-feature` or `design-solution`; do not emit unconditional implementation recommendation. - PARTIAL -> send only explicitly ready slices downstream with their blockers and owners; downstream execution cannot absorb blocked slices or claim their activation. - Write run record to `artifacts/runs/[slug]/[compactISO]-implementation-readiness.json` when writes allowed. ## Runtime Contract - Use before implementation starts to gate go/no-go. - Required inputs: matching approved task record/ticket or equivalent evidence, owner, testable ACs and design/test prerequisites applicable to each proposed slice. Missing filenames do not force repeat intake. - Return BLOCKED only when required authority/approval, owner, unclear AC, consequential design, environment, or risk remains unresolved. ## Handoff Payload - `slug`, verdict (READY/BLOCKED/PARTIAL), ready slices, blocking gaps, capability gaps, outcome report, next workflow. ## Blocking Questions - Ask max 3 at a time with a recommended default and 2-3 options. ## Output Template ```md # Implementation Readiness ## Verdict ## Ready Slices ## Blocking Gaps | Area | Gap | Owner/Input Needed | | --- | --- | --- | | [area] | [gap] | [owner/input] | ## Outcome Report {schema_version: 1, run_id: "[run-id]", slug: "[slug]", workflow: implementation-readiness, feature_status: design_ready, started_at: "[timestamp]", completed_at: "[timestamp]", requirement_trace: {brd_objectives: [], requirements: [], acceptance_criteria: [], srs: []}, completed_evidence: [], missing_evidence: [], decision_needed: [], recommended_next_workflow: implement-feature, cost: {source: unavailable}, agent: {identity: "[agent-identity]", model: "[model]"}} ## Next Workflow ## Cost Report Call `get_session_cost(workflow="implementation-readiness")` before final handoff. ``` --- Source attribution: HoangNguyen0403 Original project: https://github.com/HoangNguyen0403/agent-skills-standard License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice MIT License Copyright (c) 2026 Gabriel Moreira Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Mega AI Hub resource metadata Creator / publisher: HoangNguyen0403 Original project: https://github.com/HoangNguyen0403/agent-skills-standard Attribution basis: Upstream repository explicitly recorded in package mirror path Fields of work: Design, Operations, Product Management, Project & Program Management Roles: Business Process Analyst, Product Manager, Project Manager, Technical Product Manager, UX Designer Specialties: API, Design, Word Documents, Figma, Frontend, Git, Mobile, Playwright, Testing Tools: Confluence, Figma, GitHub, GitLab, Jira Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: cc0bd2ba729ad548bd851d5c4a9347d52c8e13a838543e5b22701269fb3630c4