# Draft Domain-Specific Requirements

Teams lose time when requirements are vague or forced into one template. This skill guides Claude, Codex, and Claude Code to create clear, testable requirements for each domain.

## Install

```bash
npx skillstore add emasoft/ghe-design
```

## Metadata

- Status: approved
- Slug: emasoft-ghe-design
- Skillstore revision: r1
- Version status: missing
- Tree hash: 3da15867206370d4bceaadd29228c7fee58f091b95d028dc1a1838df8b8fc9c0
- Author: Emasoft
- GitHub username: Emasoft
- License: MIT
- Repository: https://github.com/Emasoft/ghe-marketplace/tree/main/plugins/ghe/skills/ghe-design
- Ref: 30c73eac2afe762f6aa9c4553158769369d47351
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/emasoft-ghe-design
- Manifest: https://skillstore.pages.dev/api/skills/emasoft-ghe-design/manifest

## Capabilities

- Defines core elements that every requirements document should include.
- Provides domain patterns for algorithms, games, finance, distributed systems, and security.
- Encourages clear acceptance criteria and external references.
- Guides GHE report naming and report placement expectations.
- Explains how to adapt structure to the problem domain.

## Use Cases

- Plan a Feature Requirement: Create a concise requirement with purpose, acceptance criteria, assets, and references before implementation starts.
- Specify a Technical System: Document architecture, failure modes, data contracts, and verification steps for complex engineering work.
- Prepare Security Requirements: Capture threat models, trust boundaries, mitigations, and security headers in a format engineers can verify.

## Prompt Templates

### Create Basic Requirements

```
Use ghe-design to draft requirements for this feature: [feature]. Include what, why, acceptance criteria, and references.
```

### Adapt to a Domain

```
Use ghe-design to write requirements for [domain]. Choose sections that fit the domain and explain how completion will be verified.
```

### Expand an Existing Requirement

```
Use ghe-design to review this requirement draft: [draft]. Add missing constraints, edge cases, references, and testable acceptance criteria.
```

### Build a Cross-Discipline Specification

```
Use ghe-design to create a full requirement for [system]. Cover architecture, risks, compliance, failure modes, assets, and verification evidence.
```

## Limitations

- Does not generate executable code or run validation tools.
- Assumes the GHE agent workflow and role names.
- Contains broad instructions that may not fit every repository policy.
- Includes external references that users should verify before relying on them.

## Best Practices

- Start with the user goal, then add only sections that improve clarity.
- Make every acceptance criterion observable and testable.
- List external references without copying large source documents.

## Anti Patterns

- Do not force every requirement into the same template.
- Do not replace user requirements with silent improvements.
- Do not use vague success terms without verification evidence.

## Security Audit

- Audited at: 2026-07-05T15:47:58.44\+00:00
- Summary: Most static command and network findings are false positives from Markdown code fences, inline paths, and reference links. The audit confirms the ~/.claude write allowance and flags absolute prompt-control wording plus mandatory full-report posting.

## Stats

- Views: 265
- Downloads: 8
- Favorites: 0
- Popularity score: 0