# Initiative Feasibility

> >-

- **Type:** Skill
- **Install:** `agentstack add skill-drivestream-lab-prayog-skills-initiative-feasibility`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [drivestream-lab](https://agentstack.voostack.com/s/drivestream-lab)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [drivestream-lab](https://github.com/drivestream-lab)
- **Source:** https://github.com/drivestream-lab/prayog-skills/tree/main/skills/development/initiative-feasibility

## Install

```sh
agentstack add skill-drivestream-lab-prayog-skills-initiative-feasibility
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Initiative feasibility

Assess whether the **dev team's spec slice** for this initiative is **buildable
in this repo as it exists today**. **Do not implement** — flag only.

The spec slice is written by the dev team after reading the PRD. This skill
reviews it for gaps, codebase alignment, and architecture governance.

Pattern borrowed from awesome-copilot `create-github-issues-for-unmet-specification-requirements` (extract → search code → classify). Evaluation discipline aligned with `validate-requirements`.

## NON-NEGOTIABLE

1. Never skip a check in [references/checks.md](references/checks.md). Mark SKIPPED with reason.
2. Evidence for every finding — spec quote + repo path (file, symbol, or test name).
3. Don't fix — flag. Do not edit product source or product specs unless the user explicitly asks after the report.
4. Dual output: chat summary + saved report file + 4-lane triage.
5. Run T0–T5 control loop (Gather → Understand → Analyze → Plan → Execute → Verify).

## Inputs

Gather before starting. Resolve paths from `.harness/profile.yaml` or [references/layout-defaults.md](references/layout-defaults.md).

1. **Initiative spec slice** — primary doc (REQUIRED); written by dev team, lives under `product_spec_dir`
2. **PRD** — upstream requirements from `-meta/prd/` (OPTIONAL; for conformance context; link from spec header)
3. **As-built** — `implementation-status.md` (REQUIRED)
4. **Tests** — `tests_readme`, `unit_tests_dir`, `live_verify_dir`, and toolchain config from profile (REQUIRED)
5. **Source** — modules under `source_roots` from profile (REQUIRED)
6. **Prior feasibility report** — for incremental re-run (OPTIONAL)
7. **Layout** — `.harness/profile.yaml` or [references/layout-defaults.md](references/layout-defaults.md)
8. **`rules_glob`** — workspace MDC rules (REQUIRED). Read before T2 Analyze.
9. **`adr_dir`** — architecture decision records (REQUIRED). Run relevant-ADR pass per [references/governance.md](references/governance.md) before T2 Analyze.

## When to use

- Dev has written spec slice and wants to check buildability before spec PR merge
- After dev updates spec — re-run on changed sections
- User asks: feasibility, impact, gap analysis, spec vs codebase

## Process

1. **T0 Gather** — inventory inputs; note missing paths
2. **T1 Understand** — initiative id, spec branch, review objective
3. **T2 Analyze** — read spec waves/capabilities; scan repo evidence; cross-reference `rules_glob` and relevant ADRs; flag spec wording that conflicts with MDC patterns or Accepted ADRs
4. **T3 Plan** — which checks run (full vs incremental)
5. **T4 Execute** — run checks F1–F14 per [references/checks.md](references/checks.md)
6. **T5 Verify** — save report; publish summary + 4-lane triage

## Output

Save to `{reports_dir}/{feasibility_prefix}-{initiative}.md` (from profile).

Use [references/output-template.md](references/output-template.md).

## Open items — 4-lane triage

End with four lanes (see output template):

- **PM questions** — product scope, UX, priority; comment on **meta PRD PR** (plain English)
- **PE questions** — engineering decisions, ADR gaps, test policy; comment on **spec PR**; resolved by `/spec-technical-review`
- **Domain clarifications** — business source-of-truth; route to named SME (meta PRD PR or issue)
- **Auto-fixable** — naming drift, inferred cross-references; agent resolves on spec branch

Do **not** route engineering decisions to PM. Apply the routing rubric in
the `spec-technical-review` skill's `references/governance.md`.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [drivestream-lab](https://github.com/drivestream-lab)
- **Source:** [drivestream-lab/prayog-skills](https://github.com/drivestream-lab/prayog-skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-drivestream-lab-prayog-skills-initiative-feasibility
- Seller: https://agentstack.voostack.com/s/drivestream-lab
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.