# Spec Draft

> >-

- **Type:** Skill
- **Install:** `agentstack add skill-drivestream-lab-prayog-skills-spec-draft`
- **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/spec-draft

## Install

```sh
agentstack add skill-drivestream-lab-prayog-skills-spec-draft
```

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

## About

# Spec draft

Translate the **PRD** into a **spec slice** for this repo. The spec slice is
the engineering team's interpretation of what the PRD means for their codebase.

**Do not implement.** Produce `docs/specification/product/INIT-{id}.md` only.

## Why this skill exists

PM writes PRD in feature language. Engineers own the spec.
This skill bridges the gap — it reads the PRD and drafts structured spec FRs
that the dev team can review, edit, and then run `/initiative-feasibility` on.

## NON-NEGOTIABLE

1. The spec draft is a **starting point** — dev must review and edit before
   committing. Do not present it as authoritative without dev review.
2. Language in the spec must be **engineering terms** — FRs, acceptance criteria,
   module scope — not copied PRD user-story language.
3. Scope must be **bounded to this repo** only. Do not write FRs for other repos.
4. Every FR must trace to a named section or bullet in the PRD.
5. Flag anything in the PRD that is **ambiguous for this repo** — do not guess.
   Put ambiguities in a "Spec questions" section at the bottom.

## Prerequisites

- Meta PRD PR exists (merged or open) with impact map tech-lead LGTM
- Engineering has opened spec PR on branch `chore/INIT-{COMPONENT}-{NUMBER}-spec-{repo}`

## Inputs

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

1. **PRD** — (REQUIRED) from `-meta/prd/INIT-*.md`. Read from the meta
   PRD PR branch or merged `develop`. Do not assume PRD is on develop if PR is
   still open — use PR branch when iterating in parallel.
2. **Impact map** — (RECOMMENDED) PR comment from `/prd-impact-map` confirming
   this repo's scope.
3. **As-built** — `implementation-status.md` (REQUIRED) — understand what
   already exists before writing FRs.
4. **Source** — `source_roots` from profile — understand current module structure.
5. **Service profile** — `docs/specification/product/00-service-profile.md` if
   it exists — understand the repo's existing domain.
6. **`adr_dir`** — existing ADRs constrain what this spec can propose.
7. **Layout** — `.harness/profile.yaml` or [references/layout-defaults.md](references/layout-defaults.md)

## Process

1. **T0 Gather** — PRD path, impact map scope, as-built, source, service profile
2. **T1 Understand** — initiative id; what capabilities land in this repo per PRD
   and impact map; what already exists (as-built + source scan)
3. **T2 Scope** — list ONLY what this repo owns. Explicitly exclude what belongs
   to other repos. Cross-service contracts are noted but not spec'd here.
4. **T3 Draft** — write INIT-*.md using [references/output-template.md](references/output-template.md)
5. **T4 Flag** — list ambiguities, open questions, and anything that needs PM
   confirmation (route to meta PRD PR — see feasibility skill)
6. **T5 Present** — show draft to dev for review; do NOT commit until dev confirms

## Output

Draft saved to `{product_spec_dir}/INIT-{id}.md` (from profile).

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

## Next step

After dev reviews and edits the spec draft:

```
git add docs/specification/product/INIT-{id}.md
git commit -m "feat: spec slice for INIT-{id}"
/initiative-feasibility   ← run this on the committed spec
```

## 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-spec-draft
- 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%.