proven-needs

Orchestrates state-transition workflows for software systems from observation to validation.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/provenimpact/proven-needs --skill proven-needs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: proven-needs
Source: https://github.com/provenimpact/proven-needs/tree/main/skills/proven-needs
Command: npx skills add https://github.com/provenimpact/proven-needs --skill proven-needs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates end-to-end state-transition workflows for evolving software systems by observing current state, classifying intent, evaluating feasibility, deriving a minimal transition plan, and executing capabilities in dependency order.

Core Features & Use Cases

  • Observe current state across artifacts, codebase, dependencies, and constraints.
  • Declare desired state and decompose it into feature packages or capabilities.
  • Evaluate feasibility under constraints and staleness, and derive a minimal transition plan.
  • Execute capabilities in dependency order to apply changes and validate outcomes.
  • Record transitions in a state log for traceability and recoverability.
  • Reuse across feature work, maintenance tasks, and architecture evolution.

Quick Start

Declare your desired state and let proven-needs orchestrate the necessary capabilities to achieve it.

Frequently Asked Questions about proven-needs

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

FAQPage Schema
How do I orchestrate end-to-end state transitions for software feature evolution?▼

To orchestrate end-to-end state transitions, declare your desired state and let the system observe the current codebase, evaluate constraints, and derive a minimal transition plan to execute capabilities in dependency order.

What is the best way to manage codebase constraints and capability dependencies during maintenance?▼

Managing codebase constraints during maintenance requires evaluating feasibility under current limitations and staleness, then coordinating multiple capabilities in the correct dependency order to validate outcomes and record transitions in a state log.

How does state-transition workflow traceability work for evolving software systems?▼

State-transition workflow traceability works by recording each applied change and validated outcome in a state log, ensuring recoverability and visibility as artifacts are created and verified across the codebase and dependencies.

Can I automate feasibility checks and staleness management before applying codebase changes?▼

Yes, you can automate feasibility checks and staleness management by observing the current state across artifacts and dependencies, classifying intent, and evaluating constraints before executing any state-transition capabilities.

Do I need to manually sequence capabilities for software architecture evolution tasks?▼

No, you do not need to manually sequence capabilities for architecture evolution; the system automatically derives a minimal transition plan and executes capabilities in the correct dependency order to achieve the desired state.