claim-lifecycle

Update claim statuses in YAML and Markdown files with controlled vocabulary.

3|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/RamanEbrahimi/raman-marketplace --skill claim-lifecycle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claim-lifecycle
Source: https://github.com/RamanEbrahimi/raman-marketplace/tree/main/plugins/agentic-research/skills/claim-lifecycle
Command: npx skills add https://github.com/RamanEbrahimi/raman-marketplace --skill claim-lifecycle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill manages the lifecycle of claims, ensuring controlled vocabulary and protocol adherence for claim status updates.

Core Features & Use Cases

  • Controlled Status Chain: Manages claim statuses from 'question' to 'refuted' with defined protocols.
  • Proofing and Promotion: Ensures claim promotion through a structured process with evidence requirements.
  • Project Updates: Integrates with project.yaml and conjectures/conjectures.md for claim status updates.
  • Use Case: Ideal for managing research claims where evidence-based status updates are crucial.

Quick Start

Update the status of claim 'C1' to 'proved' by reviewing the evidence and confirming in chat.

Frequently Asked Questions about claim-lifecycle

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

FAQPage Schema
How do I manage research claim statuses with a controlled vocabulary?

Claim statuses are managed by transitioning from 'question' to 'refuted' using a controlled vocabulary and structured proofing protocols. This enforces evidence-based status updates within YAML and Markdown files.

How do I update claim statuses in project.yaml using structured protocols?

You update claim statuses in project.yaml by applying structured proofing protocols that require reviewing evidence and user approval. Status changes synchronize between project.yaml and conjectures.md files.

What is the status chain for managing claims from question to refuted?

The status chain for managing claims transitions a claim from a 'question' to 'refuted' through defined intermediate statuses. This controlled vocabulary ensures claims are promoted or refuted only after meeting evidence requirements.

Do I need YAML and Markdown files to track claim lifecycles?

Yes, tracking claim lifecycles requires YAML and Markdown files to store and manage status updates. The process specifically integrates with project.yaml and conjectures/conjectures.md for status tracking.

How does claim promotion work with evidence requirements?

Claim promotion works by enforcing a structured proofing process where evidence is reviewed and user approval is obtained. This ensures a claim's status update is valid before being recorded in the project files.