# Design Features Through Guided Planning

Feature ideas often lack clear requirements, tradeoffs, and implementation steps. This skill guides discovery, design validation, documentation, and task planning through structured dialogue.

## Install

```bash
npx skillstore add notedit/feature-design-assistant
```

## Metadata

- Status: approved
- Slug: notedit-feature-design-assistant
- Skillstore revision: r1
- Version status: missing
- Tree hash: 63df1dfcb2f32116eddc34a7331bcbd37e493f6070af8f9d47f68f1862410b84
- Author: notedit
- GitHub username: notedit
- License: MIT
- Repository: https://github.com/notedit/happy-coding-agent/tree/main/skills/feature-design-assistant
- Ref: e397ce5a135369cd6def89cb6400d013e2f68f2f
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/notedit-feature-design-assistant
- Manifest: https://skillstore.pages.dev/api/skills/notedit-feature-design-assistant/manifest

## Capabilities

- Explores project structure and existing patterns before planning a feature.
- Collects core, technical, integration, and documentation requirements through batched questions.
- Compares two or three implementation approaches with pros and cons.
- Builds sectioned design documents covering architecture, data, API, components, errors, and tests.
- Produces implementation task checklists with priorities, dependencies, files, and estimates.

## Use Cases

- Plan a New Feature: A product engineer can turn a broad idea into requirements, architecture, and task breakdowns before coding.
- Compare Implementation Approaches: A technical lead can evaluate options, risks, dependencies, and quality requirements with clear tradeoffs.
- Prepare an Implementation Handoff: A developer can create design documentation and ordered tasks for a later coding session.

## Prompt Templates

### Start Feature Discovery

```
Help me design a small feature. Start by asking the core requirement questions and then summarize the answers.
```

### Plan Across System Layers

```
Review this repository context and help design [feature]. Ask technical, dependency, and documentation questions before proposing approaches.
```

### Evaluate Architecture Options

```
Design [feature] for a system with [constraints]. Compare three approaches, recommend one, and validate each design section before handoff.
```

### Create Implementation Handoff

```
Use this skill to produce a full implementation handoff for [feature]. Include requirements, architecture, API, error handling, tests, and prioritized tasks.
```

## Limitations

- It is a planning workflow, not an implementation engine.
- It depends on accurate user answers and repository context.
- It does not validate generated designs by running tests.
- It may need adaptation when AskUserQuestion tooling is unavailable.

## Best Practices

- Share repository context and existing feature patterns before answering design questions.
- Choose recommendations only after reviewing tradeoffs, dependencies, and quality requirements.
- Validate each design section before moving to implementation tasks.

## Anti Patterns

- Using the workflow for tiny changes that only need a direct edit.
- Skipping requirement questions and asking for a final design immediately.
- Treating generated tasks as verified estimates without developer review.

## Security Audit

- Audited at: 2026-07-06T20:08:45.351\+00:00
- Summary: All 24 static findings are false positives caused by Markdown code fences or inline backticks in SKILL.md. The skill is a documentation-only planning workflow, and I found no prompt injection, data exfiltration intent, or command execution instructions.

## Stats

- Views: 188
- Downloads: 14
- Favorites: 2
- Popularity score: 0