contract-decompose

Decomposes large contracts into dependency-ordered smaller ones with JIRA integration and risk flagging.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jira, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

The Skill unit solves the problem of handling large and complex contracts that are too vast for automated implementation, enabling the breaking down of these contracts into smaller, manageable parts.

Core Features & Use Cases

  • Decomposition of Contracts: Turns a single large contract into a series of smaller contracts with a dependency-ordered structure.
  • Flagging Risks: Identifies high-risk areas like schema migrations and authentication changes and flags them for manual handling.
  • JIRA Integration: Generates JIRA tickets linked to child contracts, providing a full lifecycle plan and dependency tracking.

Quick Start

Use the /contract decompose <ID> command with the contract you wish to break down into manageable parts.

Frequently Asked Questions about contract-decompose

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

FAQPage Schema
How do I break down a large contract into manageable pieces for automated implementation?

Large contract decomposition splits a massive contract into smaller, dependency-ordered child contracts to make automated implementation tractable. This process structures the project lifecycle and identifies critical areas requiring manual oversight.

How does JIRA integration work for tracking decomposed contract dependencies?

JIRA integration generates linked tickets for each child contract, providing full lifecycle tracking and automated dependency resolution. This maps the decomposed contract structure directly into your project management workflow.

Can I automatically flag high-risk areas like schema migrations during contract decomposition?

Yes, contract decomposition automatically identifies and flags high-risk areas such as schema migrations and authentication changes. These critical sections are explicitly marked for manual handling before project tracking begins.

Do I need a JIRA account to use contract decomposition for project management?

Yes, JIRA integration is required to generate linked tickets and facilitate project tracking. You must have JIRA configured to utilize the full lifecycle planning and dependency tracking features.

What is the best way to manage dependencies when splitting large contracts?

The best way to manage dependencies is by using contract decomposition to create a structured, dependency-ordered breakdown of child contracts. This automated resolution ensures correct implementation sequencing.

What are the limitations of automated contract decomposition for project tracking?

Automated contract decomposition cannot fully implement large contracts without human intervention. High-risk areas like authentication changes and schema migrations must be manually handled, requiring human oversight for safe execution.