Menú
Assess source acceptance coverage before MoonSpec planning.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Refresh MoonMind services from git by fetching and pinning a branch snapshot, pulling compose images, then restarting changed containers with optional orchestrator inclusion.
Provide the shared fan-out engine used by provider-specific Jira and GitHub batch presets to enqueue child workflows with inherited runtime and stable evidence.
Discover open Dependabot version-bump PRs and enqueue one `pr-resolver` workflow for each.
Master orchestrator to resolve a PR by diagnosing state and delegating to specialized skills.
Verify a GitHub issue against the current repository state, then post a GitHub issue comment with a PASS, PARTIAL, FAIL, or BLOCKED verdict. Works in two modes: (a) feature-branch mode, comparing a checked-out branch to its base ref; or (b) main/trunk mode, verifying that an issue is already implemented on the current default branch. Optionally close the issue as completed after a PASS. Use when a user asks whether a branch or merged change completes a GitHub issue, or needs an issue-visible verification comment.
Resolve GitHub PR feedback end-to-end for the branch you are on. Use when you need to fetch all comments on the branch PR, evaluate whether each comment still applies, decide whether it should be addressed, implement fixes, run compile/tests with retry-on-failure, then commit and push the result.
| name | moonspec-assess |
| description | Assess source acceptance coverage before MoonSpec planning. |
| metadata | {"required-capabilities":["git"]} |
Use this skill after moonspec-specify and before moonspec-plan when a source-backed spec may include artifacts/moonspec/source-acceptance.json.
Before assessing, resolve the active feature directory and feature identifier from .specify/feature.json or the selected specs/<feature>/spec.md. Consume artifacts/moonspec/source-acceptance.json only when its featureId matches the active feature. If the artifact is absent or belongs to a different feature, report not_applicable and do not write or require an assessment artifact for this story.
Write artifacts/moonspec/acceptance-assessment.json with schema version v1 and the same featureId as the active feature and source acceptance matrix.
External systems can provide a matrix, but MoonSpec stays provider neutral.
Allowed overall verdicts:
FULLY_IMPLEMENTEDPARTIALLY_IMPLEMENTEDNOT_IMPLEMENTEDBLOCKEDNO_DETERMINATIONAllowed row statuses:
VERIFIEDPARTIALMISSINGCONFLICTUNVERIFIEDOUT_OF_SCOPEProduce boundedBacklog for every missing, partial, conflict, or required-unverified row. The backlog is the authoritative implementation backlog for downstream planning, tasks, implementation, and verification.
Do not choose FULLY_IMPLEMENTED unless every repo-verifiable source row is verified and every manual/provider-only row is explicitly scoped.