facts-refine

Refines draft facts into actionable specifications by resolving ambiguities, gaps, and contradictions.

3.2k|219|Updated Jul 27, 2024

Search Tags:#specification writing #fact management #fact validation #fact refinement #fact transition

Ready to run

npx skills add https://github.com/av/harbor --skill facts-refine

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: facts-refine
Source: https://github.com/av/harbor/tree/main/.agents/skills/facts-refine
Command: npx skills add https://github.com/av/harbor --skill facts-refine

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps in transforming draft facts into clear, actionable specifications by resolving ambiguities, filling gaps, and eliminating contradictions.

Core Features & Use Cases

Fact Refinement: Convert draft facts into precise specifications through collaborative conversation.
Issue Identification: Scan for structural, vague, gap, contradiction, compound, domain vocabulary, and missing validation issues.
User Collaboration: Work with the user to discuss and apply changes to facts.
Fact Transition: Transition facts from @draft to @spec with clear instructions.
Verification: Verify and summarize changes made to the fact sheet.

Quick Start

Start refining draft facts by running 'facts list' to identify @draft facts and then proceed with the defined process.

Frequently Asked Questions about facts-refine

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

FAQPage Schema

How do I refine draft facts into precise specifications?▼

To refine draft facts into precise specifications, this process identifies and resolves structural issues like vagueness, gaps, and contradictions. It requires collaborative discussion with you to apply changes and transition facts from draft status to spec.

What issues should I look for when writing fact specifications?▼

When writing fact specifications, you should look for vagueness, gaps, contradictions, compound facts, domain vocabulary issues, and missing validation. Identifying these issues ensures your draft facts become clear and actionable.

How do I transition facts from draft to spec status?▼

To transition facts from draft to spec status, you run a fact listing command to identify draft facts, collaboratively discuss identified issues, apply changes, and verify the updates. This process ensures a clear transition to actionable specifications.

Can I automate fact validation without user collaboration?▼

No, fact validation and refinement cannot be fully automated without user collaboration. The process requires interactive discussion with you to resolve ambiguities, fill gaps, and apply changes to transition facts effectively.

What is the best way to resolve compound facts in specification writing?▼

The best way to resolve compound facts in specification writing is to scan for them during refinement, discuss the overlapping elements collaboratively, and split them into distinct, actionable specifications through user-confirmed changes.