deliverable

Coordinates multi-session projects into deliverables with provenance and handoff.

Updated Aug 23, 2026

Search Tags:#artifacts #handoff #multi-session #deliverable #project-management #state-doc

Ready to run

npx skills add https://github.com/paulyokota/FeedForward --skill deliverable

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deliverable
Source: https://github.com/paulyokota/FeedForward/tree/main/.claude/skills/deliverable
Command: npx skills add https://github.com/paulyokota/FeedForward --skill deliverable

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a project-structure playbook for multi-session initiatives, ensuring concrete deliverables and clear handoffs across sessions.

Core Features & Use Cases

Provides a project-level structure with inputs, state, and artifacts to support cross-session handoffs.
Enforces provenance and evidence provenance for all claims guiding the deliverable.
Supports phased work from research to proposal to execution with a centralized state doc.

Quick Start

Start by establishing the state doc, seed the inputs with initial data, then draft the deliverable from the inputs.

Frequently Asked Questions about deliverable

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

FAQPage Schema

How do I manage project handoffs across multiple sessions?▼

To manage multi-session project handoffs, you need a centralized state doc that tracks inputs, artifacts, and deliverables. This ensures cross-session consistency by enforcing an inputs-to-deliverable workflow with provenance governance.

What is the best way to structure long-running project artifacts?▼

Structuring long-running project artifacts requires separating inputs, a state doc, and the final deliverable. This approach enforces evidence provenance for all claims and supports phased work from research to execution with clear handoffs.

How do I maintain state consistency for a project across different sessions?▼

Maintaining state consistency across sessions requires a centralized state doc that enforces cross-session consistency constraints. This doc coordinates artifact governance and tracks provenance from initial inputs to the final deliverable.

Can I use a state doc to track provenance for project deliverables?▼

Yes, a state doc can track provenance for project deliverables by enforcing evidence provenance for all guiding claims. It coordinates phased work from research to proposal to execution, ensuring concrete deliverables with structured artifacts.

Do I need to establish a state doc before drafting multi-session deliverables?▼

Yes, you must establish a centralized state doc and seed it with initial input data before drafting the deliverable. This enforces the inputs-to-deliverable workflow required for cross-session handoff and artifact governance.

Why does my multi-session project fail to produce concrete deliverables?▼

Multi-session projects fail to produce concrete deliverables without an enforced inputs-to-deliverable workflow and artifact governance. A centralized state doc is required to maintain cross-session consistency and ensure provenance for all claims.