harness-plan

Generate structured Sprint Contracts from project dev-guides and update workflow state.

3|1|Updated May 1, 2026
One-click install
npx skills add https://github.com/bigbulgogiburger/claude_jira_harness --skill harness-plan-bigbulgogiburger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-plan
Source: https://github.com/bigbulgogiburger/claude_jira_harness/tree/main/skills/harness-plan
Command: npx skills add https://github.com/bigbulgogiburger/claude_jira_harness --skill harness-plan-bigbulgogiburger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation and management of detailed Sprint Contracts based on dev-guides, reducing manual documentation effort and ensuring consistency across project planning.

Core Features & Use Cases

  • Sprint Contract Generation: Reads project dev-guides to produce structured Sprint Contracts including DoD, verify targets, and scope.
  • Workflow State Management: Updates a shared workflow state file to track progress and maintain synchronization across tools.
  • Use Case: A project team wants to quickly generate a comprehensive Sprint Contract aligned with their dev-guide, then automatically update their workflow state for subsequent steps.

Quick Start

Invoke /harness-plan with your project issue key to automatically generate and save the Sprint Contract, updating internal project state accordingly.

Frequently Asked Questions about harness-plan

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

FAQPage Schema
How do I automate sprint contract generation from dev-guides?

Sprint contract generation is automated by reading project dev-guides to produce structured definitions including DoD, verify targets, and scope. This reduces manual documentation effort and ensures consistency across project planning.

What is a sprint contract and why do I need it for project planning?

A sprint contract is a structured definition for an Agile sprint that includes Definition of Done, verify targets, and scope. It is needed to maintain consistent development standards and clear sprint boundaries for engineering teams.

Can I use this workflow automation for Agile teams without configuring environment variables?

Environment variable checks are required for this workflow automation to function correctly. The system implements these checks alongside project detection heuristics to manage file system state synchronization for Agile teams.

How does workflow state management work during project planning?

Workflow state management updates a shared state file to track progress and maintain synchronization across tools during project planning. This ensures subsequent steps in the development workflow have access to current sprint definitions.

What is the best way to keep sprint definitions synchronized with development guides?

The best way to keep sprint definitions synchronized is to automate generation directly from development guides using file system management. This approach updates internal project state automatically whenever dev-guides change.

What are the limitations of automating sprint contracts using project detection heuristics?

Limitations of automating sprint contracts via project detection heuristics include dependency on accurate environment variable configuration and existing dev-guide structures. The system requires proper file system access to maintain state synchronization without errors.