manage-findings

Manage plan and per-phase Q-Gate findings via JSONL CLI workflows.

4|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/cuioss/plan-marshall --skill manage-findings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-findings
Source: https://github.com/cuioss/plan-marshall/tree/main/marketplace/bundles/plan-marshall/skills/manage-findings
Command: npx skills add https://github.com/cuioss/plan-marshall --skill manage-findings

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Unified storage and lifecycle management for plan-level findings and per-phase Q-Gate findings, reducing fragmentation and manual tracking across plans and phases.

Core Features & Use Cases

  • Unified storage: JSONL-based persistence for plan findings and per-phase Q-Gate findings under the .plan directory.
  • Lifecycle management: Supports types, severities, resolutions, and promotion state with deterministic hash IDs and per-phase workflows.
  • CLI-driven workflows: Provides add, query, get, resolve, promote, and qgate operations to streamline planning, execution, and governance.

Quick Start

Run the manage-findings CLI to add a finding for a plan, then query and resolve as needed.

Frequently Asked Questions about manage-findings

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

FAQPage Schema
How do I store and track plan-level findings across multiple phases?

Plan-level findings are stored using JSONL-based persistence under the .plan directory, enabling unified tracking across phases. The CLI supports adding, querying, and resolving findings to reduce manual fragmentation throughout the plan lifecycle.

What is a Q-Gate findings workflow in plan execution?

A Q-Gate workflow manages per-phase verification issues during plan execution, from refinement to finalization. It provides CLI operations to add, query, promote, and resolve phase-specific findings, ensuring governance at each stage.

How do I add and resolve findings using a CLI for project planning?

Use the manage-findings CLI to add findings with deterministic hash IDs, then query and resolve them as needed. The CLI handles types, severities, and resolution states, streamlining execution and governance workflows.

Can I promote per-phase findings to long-lived plan findings?

Yes, per-phase Q-Gate findings can be promoted to long-lived plan-level findings using the CLI's promote operation. This supports lifecycle management by elevating phase-specific verification issues into persistent plan findings.

Does JSONL storage work for managing plan findings and governance issues?

JSONL storage persists both plan-level findings and per-phase Q-Gate findings under the .plan directory. This format supports deterministic hash IDs, lifecycle states, and CLI-driven management for execution and governance workflows.

What are the limitations of CLI-based findings lifecycle management?

The findings lifecycle management relies on JSONL persistence under the .plan directory, meaning storage is local to the plan context. It focuses on plan execution and governance workflows, covering findings from refinement to finalization phases.