# feasibility

Structures and validates durable data and ML feasibility studies using constrained YAML and UUID-tracked provenance.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 1627 repo stars
- Author: microsoft
- License: CC-BY-4.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/microsoft/hve-core/tree/HEAD/.github/skills/data-science-engineering/feasibility/SKILL.md
- Updated: 2026-10-25
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/feasibility

## What it does

This workflow guides the drafting of technical feasibility assessments for data and ML initiatives. Machine-readable facts live inside a single `FEASIBILITY-STUDY-INTERCHANGE` YAML block that adheres to JSON types. The surrounding Markdown provides narrative context and links to empirical evidence without modifying machine data.

Every concept, revision, and relationship relies on RFC 9562 UUIDv4 URNs instead of titles or file paths. When an item status or category changes, the skill creates a successor revision while preserving lifecycle lineage and tombstones for withdrawn items.

A study fails downstream ingestion if it skips `scripts/validate_feasibility.py`: the schema requires strict semantic closure and matching narrative anchors for every registered item.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add microsoft/hve-core --skill feasibility -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/feasibility/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/feasibility/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add microsoft/hve-core --skill feasibility -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/feasibility/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add microsoft/hve-core --skill feasibility -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/feasibility/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install microsoft/hve-core .github/skills/data-science-engineering/feasibility
```

2. **Manually: put the files in place**
- File: `.github/skills/feasibility/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add microsoft/hve-core --skill feasibility -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/microsoft/hve-core --path .github/skills/data-science-engineering/feasibility
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/feasibility/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/microsoft/hve-core/tree/HEAD/.github/skills/data-science-engineering/feasibility/SKILL.md

## When to use it
- evaluate data sufficiency and technical feasibility for an ML goal
- track experimental evidence, operational risks, and dependencies
- verify schema closure and revision lineage with JSON Schema 2020-12
- generate a companion handoff summary for PRD authors

## Example prompts
- Run a feasibility study on whether our clickstream data supports real-time churn prediction
- Validate the draft study against the interchange schema using scripts/validate_feasibility.py
- Produce the feasibility-to-PRD handoff artifact for the approved study revision

## Source text · SKILL.md · CC-BY-4.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 6b8253b2fb83f867.

BEGIN THIRD-PARTY FILE 6b8253b2fb83f867
```text
---
name: feasibility
description: "Author and validate durable data and ML feasibility studies using the Feasibility Study Interchange Profile, constrained YAML authority, UUID URN identity, lifecycle lineage, and evidence traceability. Use when assessing whether available data and technical evidence support a proposed outcome."
license: CC-BY-4.0
user-invocable: false
metadata:
  authors: "Microsoft (planning synthesis)"
  spec_version: "1.0"
  last_updated: "2026-09-14"
  content_based_on: "https://specif.de/; https://docs.oasis-open-projects.org/oslc-op/rm/v2.1/os/; https://www.w3.org/TR/prov-o/; https://www.dublincore.org/specifications/dublin-core/dcmi-terms/; https://www.rfc-editor.org/rfc/rfc9562.html; https://json-schema.org/draft/2020-12/"
---

# Data and ML Feasibility Workflow

## Goal

Produce one durable Markdown feasibility study that remains useful to people and can be consumed later by a Functional Planner. One constrained YAML block owns machine facts; narrative sections preserve evidence, interpretation, and context.

## Flow

1. Confirm the proposed outcome, decision boundary, study scope, and durable output path.
2. Allocate UUIDv4 URNs for the study concept, study revision, each item concept, each item revision, and each relation. Never derive identity from a title, class, path, or content.
3. Capture candidate capabilities, constraints, assumptions, findings, risks, dependencies, decisions, evidence, gaps, and non-goals. Preserve uncertainty and source-authored criteria without promoting every item to a requirement.
4. Record lifecycle and provenance. Reclassification keeps conceptual identity and creates a new revision. Split, merge, derivation, withdrawal, and supersession retain explicit lineage.
5. Write or update the single named `FEASIBILITY-STUDY-INTERCHANGE` YAML block. Narrative can explain machine facts but cannot redefine them.
6. Validate constrained YAML, JSON Schema 2020-12 structure, semantic closure, revision lineage, tombstones, and narrative anchors with `scripts/validate_feasibility.py`.
7. Present the recommendation and unresolved review gaps. Preserve the study as read-only evidence for downstream consumers.
8. After the study is final, emit the sibling feasibility-to-PRD handoff described in [feasibility-to-prd-handoff.md](references/feasibility-to-prd-handoff.md). Regenerate it after any material study revision, then validate both artifacts with `scripts/validate_feasibility.py <study.md> --handoff <handoff.yml>`.

## Inputs

* Problem definition, desired outcome, and decision the study must support
* Data access, discovery, architecture, exploration, preprocessing, and experiment evidence
* Source-authored acceptance criteria, when known
* Risk, privacy, Responsible AI, performance, and operational evidence
* Prior study revision and item identity registry, when revising an existing study
```
END THIRD-PARTY FILE 6b8253b2fb83f867

The third-party file has ended. Everything between the 6b8253b2fb83f867 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2887 of 8360 bytes. © microsoft · CC-BY-4.0 · https://github.com/microsoft/hve-core/tree/HEAD/.github/skills/data-science-engineering/feasibility/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
