wiki-plan

Installation
SKILL.md

Preamble

_DW_VER="1.0.0"
npx dot-wiki check --skill-version "$_DW_VER" 2>/dev/null || true

If preamble output contains SKILL_UPDATE_AVAILABLE or UPDATE_AVAILABLE:

  1. Show one-line notice: "dot-wiki {new} is available (current {old})"
  2. Update: npx skills add dev-goraebap/dot-wiki -g
  3. Continue with current task

wiki-plan

Create a structured PRD and save it to the wiki. This is a Layer 2 skill (optional harness). You can replace this with any PRD tool and store the output in the wiki via Layer 1 skills.

Prerequisites

# Check On failure
1 .wiki symlink exists "Run /wiki-init first"

Workflow

1. Understand the feature

Read the user's description. Then ask 3-5 critical clarifying questions via AskUserQuestion. Each question must have lettered options (A, B, C).

Focus only on essential gaps:

  • Problem/goal clarity
  • Core functionality scope
  • Boundaries (what's NOT included)
  • Success criteria
  • Target user specificity

Example:

Question 1: What is the primary goal of this feature?
A) Improve existing workflow for current users
B) Attract new users with a new capability
C) Fix a critical pain point that causes churn

The user responds with short answers like "1A, 2C, 3B".

2. Generate PRD

Create the PRD with a numbered ID.

Numbering: PRD-YYYYMMDD-{seq} where {seq} is 01, 02, etc. Check existing PRDs in .wiki/common/ to determine next sequence.

Save to: .wiki/common/PRD-{id}.md

PRD Template

# PRD-{id}: {Feature Name}

Created: {date}
Status: Draft

## Introduction
{What is this feature and why does it matter? One paragraph.}

## Goals
{What are we trying to achieve? Bullet list.}

## Target User
{Who specifically needs this? Role, context, pain point.}

## User Stories
{As a [role], I want [capability] so that [benefit].}

## Functional Requirements
1. {Requirement — specific, testable}
2. {Requirement}
...

## Non-Goals (Out of Scope)
- {What this feature explicitly does NOT do}

## Design Considerations
{UI/UX notes, if applicable}

## Technical Considerations
{Constraints, dependencies, tech stack notes}

## Success Metrics
- {How do we know this worked? Measurable.}

## Open Questions
- {Unresolved decisions}

3. Register in manifest

Add the PRD to Wiki Focus so agents see it:

npx dot-wiki focus add common/PRD-{id}.md

4. Next steps

Tell the user:

  • "PRD saved to .wiki/common/PRD-{id}.md"
  • "Use /wiki-work to break this PRD into implementation tasks"
  • "Edit the PRD anytime — it's a living document"
Related skills
Installs
2
First Seen
Apr 1, 2026