closeout-filing

Files SDLC closeout observations as deduplicated ADO work items under a findings epic.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/PolyphonyRequiem/twig --skill closeout-filing-polyphonyrequiem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: closeout-filing
Source: https://github.com/PolyphonyRequiem/twig/tree/main/.github/skills/closeout-filing
Command: npx skills add https://github.com/PolyphonyRequiem/twig --skill closeout-filing-polyphonyrequiem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a conductor SDLC run completes, its closeout observations and improvement suggestions are easy to lose or file twice. This Skill turns that closeout JSON into actionable Azure DevOps Issues and Tasks, deduplicating against existing items so nothing is double-filed. ## Core Features & Use Cases - Automated Filing: Creates a closeout Issue under the Closeout Findings epic (#1603) and Tasks for each improvement, with markdown descriptions containing context, rationale, and acceptance criteria. - Semantic Deduplication: Scans the existing findings tree via twig and cross-references each improvement by meaning, not exact text, to avoid duplicates. - SDLC Chaining: Accepts the observations and improvements output directly from a completed twig-sdlc conductor run. - Use Case: After running conductor run twig-sdlc-full@twig on an epic, pass the closeout output to this workflow to file all findings in minutes instead of manually creating each work item. ## Quick Start Ask the agent to file the closeout findings from your completed SDLC run by providing the epic ID, observations, and improvements list.

Frequently Asked Questions about closeout-filing

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

FAQPage Schema
How do I file closeout findings as ADO work items?

Run the closeout-filing@twig conductor workflow with the epic ID, observations text, and improvements list as inputs. It scans existing items, deduplicates, then creates a closeout Issue and Tasks under the Closeout Findings epic.

How does closeout filing avoid duplicate work items?

The scanner phase reads the entire Closeout Findings tree via twig and semantically compares each improvement against existing tasks by meaning, not exact text. Duplicates are excluded from the filing plan unless you pass skip_dedup=true.

Can I chain closeout filing after a twig-sdlc conductor run?

Yes. A completed twig-sdlc run outputs observations and improvements in its closeout JSON. Pass those values directly as inputs to the closeout-filing@twig workflow to file them without manual reformatting.

What prerequisites does the closeout filing workflow need?

You need the conductor skill installed, the twig conductor registry added from the twig-conductor-workflows source, the twig CLI configured with an ADO workspace, and a completed SDLC run with closeout observations.

When should I not use automated closeout filing?

Do not use it for bugs or feature requests unrelated to closeout observations, or when the findings were already filed. Check the Closeout Findings epic tree first to confirm the items do not already exist.