--- title: "pocketfm-manifest" description: "PocketFM's portable PRD-to-production workflow: Ready Check, contracts, implementation, verification, launch, and postmortems." canonical: https://agentpluginsdirectory.com/plugins/pocketfm-manifest last-updated: 2026-10-21 --- # pocketfm-manifest PocketFM's portable PRD-to-production workflow: Ready Check, contracts, implementation, verification, launch, and postmortems. - Slug: pocketfm-manifest - Publisher: PocketFM - Repository: https://github.com/iampawan/Manifest - Manifest: plugin.json - Version: 0.43.0 - Category (editorial): productivity - Skills: 28 (bug-triage, code-review, contract-decompose, contract-new, contract-pickup, contract-promote, contract-status, contract-verify, critic-code-context, critic-comms-completeness, critic-edge-cases, critic-instrumentation, critic-minimality, critic-perf-budget, critic-platform-parity, critic-regression, critic-scalability, critic-security, implement, launch-report, quick-fix, ready-check, rollback-guard, rollback-postmortem, setup-check, setup-init, tutorial, verify-deployment) - MCP servers: 1 (manifest) - Stars: 5 - Repository created: 2026-05-20 - Repository last pushed: 2026-09-02 - Publisher type: User - Listing: https://agentpluginsdirectory.com/plugins/pocketfm-manifest - Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json ## What pocketfm-manifest does, in the publisher's words A portable Agent Plugin and MCP server that takes a PRD ("contract") through the full lifecycle, spec → implement → ship → land, with quality gates that won't let an under-specified spec progress. It runs in Claude Code/Cowork, Cursor, Codex, and other agents through native skills, MCP, or the generated AGENTS.md fallback. The contract lives as markdown in your repo at.manifest/contracts/*.md. Critics produce findings as adjacent files. Reports are committed alongside. Git is your audit trail; no external database required. > New here? Read FLOW.md: the single "who runs what, when" map of > the whole lifecycle (PM → Dev → Lead → Auto), with a 30-second "which command > do I run?" guide. - Deterministic layer (scripts/validate.mjs): real code that checks everything mechanical: every behavior has instrumentation / perf budget / comms states, every behavior has an acceptance criterion, platforms are in scope, sizing arithmetic, and the readiness verdict. 100% reproducible, free (no tokens), unit-testable. From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/iampawan/Manifest/HEAD/README.md ## Skills - bug-triage: Scan Sentry, support tickets, and app store reviews for new bug clusters; deduplicate against existing tickets; file to JIRA with contract back-references; then route each new cluster back into the pipeline (trivial→/fix, substantial→/contract) with propose-by-default guardrails. Invoked nightly by… - code-review: Review a PR diff for code-level defects, security, correctness, performance, and maintainability, and post a severity-tagged review comment. Runs at the PR stage AFTER implementation, complementing verify-pr (which checks contract/AC conformance). Invoked by /code-review or the pr-verify.yml work… - contract-decompose: Turn a Large contract into a dependency-ordered sequence of Small/Medium child contracts, with risky parts (migrations, auth) flagged as human-led. Use when a contract is sized Large and the user says "decompose", "break this down", "split this epic", or invokes `/contract decompose `. Large is… - contract-new: Author a new Manifest contract from a rough idea, a one-liner, OR a link to an existing source of truth, JIRA ticket, Linear issue, Notion page, Confluence doc, GitHub issue, or Figma file. Use when the user says "new contract", "draft PRD", "spec out a feature", "pull contract from this JIRA tick… - contract-pickup: The canonical Spec entry for Manifest. Dev gives any source, JIRA / Linear / Notion / Confluence / Google Doc / Slack message / GitHub issue / Figma URL, pasted text, an image, or a free-form description, and the agent does the code archaeology, drafts the contract, runs the critics + a Figma des… - contract-promote: Freeze a verified contract into an immutable revision and start the SLA timer. Use when the user says "promote contract", "ship this PRD", "start the pipeline", or invokes `/contract promote `. Creates a JIRA epic, opens a tracking issue, kicks off implementation. - contract-status: Show the current status of a contract (or all in-flight contracts) right in the CLI, phase, SLA time-left (IST + UTC), readiness, and the next action. Use when the user says "status", "where are we", "what's in flight", "time left", or invokes `/status []`. - contract-verify: Verify a contract using a two-layer approach, a deterministic code validator first, then LLM judgment critics. Produces a consolidated findings file with a computed readiness verdict. Use when the user says "verify contract", "check this PRD", "run critics", or invokes `/contract verify `. - critic-code-context: Dev-side critic for the pickup flow. Surfaces auto-fillable defaults the agent can pull straight from the repo + history (Bucket A in contract-pickup), and code-context dev-decides items where engineering judgment is needed (Bucket B). Different from critic-regression: that one flags *risks*; this… - critic-comms-completeness: Critic that ensures every behavior specifies empty, loading, success, and error states (UI copy + notifications). Invoked by contract-verify. Catches the "we forgot the error message" bug class. - critic-edge-cases: Critic that scans a Failsafe contract for missing edge cases, ambiguous scenarios, and unspecified failure modes. Invoked by the contract-verify orchestrator. Returns findings as a JSON array. - critic-instrumentation: Critic that ensures every behavior carries an analytics event and that success metrics map to a fireable event. The keystone for post-launch verification. Invoked by contract-verify. - critic-minimality - critic-perf-budget - critic-platform-parity - critic-regression - critic-scalability - critic-security - implement - launch-report - quick-fix - ready-check - rollback-guard - rollback-postmortem - setup-check - setup-init - tutorial - verify-deployment Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized. ## MCP servers - manifest: transport: stdio; command: node ${PLUGIN_ROOT}/tools/manifest-mcp/server.mjs Read from the plugin's own mcp.json. Environment variable names only, never values.