contract-pickup

Convert PRDs from JIRA, Slack, or Google Docs into build-ready specs.

3|Updated May 20, 2026
One-click install
npx skills add https://github.com/iampawan/Manifest --skill contract-pickup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: contract-pickup
Source: https://github.com/iampawan/Manifest/tree/main/skills/contract-pickup
Command: npx skills add https://github.com/iampawan/Manifest --skill contract-pickup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires JIRA, Slack, Notion, Confluence, Google Doc, Figma, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the process of converting a Product Requirements Document (PRD) into a build-ready spec, and manages the workflow from start to ship, ensuring quality gates are met without PM intervention.

Core Features & Use Cases

  • Spec Entry: Accepts PRD sources in various formats (JIRA, Slack, Google Doc, etc.) and automates code archaeology and contract drafting.
  • Quality Checks: Performs inline verification, including critics for edge cases, security, and platform parity.
  • Feedback Loop: Routes decisions and questions to PMs via their preferred channels, keeping them informed and reducing bottlenecks.
  • Use Case: A developer can initiate the process by saying "pick up this PRD" and the Skill will automatically fetch the PRD, run quality checks, and prepare a feedback card.

Quick Start

Use the contract-pickup skill to process the PRD at 'https://example.com/prd-document'.

Frequently Asked Questions about contract-pickup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate PRD processing from JIRA or Google Docs into build-ready specs?

Automating PRD processing involves fetching source documents from JIRA or Google Docs, performing code archaeology, and drafting build-ready contracts automatically. The workflow accepts various input formats and routes decisions back to PMs via Slack to reduce bottlenecks.

What are the best ways to run quality assurance checks during PRD to ship workflows?

To run quality assurance during PRD to ship workflows, you can enforce automated inline verification gates. These checks automatically evaluate edge cases, security vulnerabilities, and platform parity without requiring manual PM intervention throughout the development lifecycle.

Does this PRD automation workflow support integrations with Confluence and Figma?

Yes, this PRD automation workflow supports integrations with Confluence and Figma. It is designed to ingest specification data from multiple external systems, alongside JIRA, Slack, and Google Docs, to create a seamless spec-to-ship pipeline.

Can I use Slack for PM collaboration and feedback routing during spec to ship automation?

You can use Slack for PM collaboration by automating feedback loops directly to PM channels. The workflow routes decisions, edge case questions, and feedback cards to PMs via their preferred channels, keeping them informed and reducing manual bottlenecks.

What configuration is needed for cross-repo regression checks in specification automation?

Cross-repo regression checks in specification automation require proper external system configuration before execution. You must establish connections to your repositories and project management tools to ensure the quality gates function correctly across multiple codebases.

Why do automated edge case critics fail during contract drafting from a PRD?

Automated edge case critics may fail during contract drafting if the initial PRD lacks sufficient detail or if external system integrations like JIRA or Confluence are improperly configured, preventing the quality gates from validating platform parity and security requirements.