docfactory-init

Original：🇺🇸 English

Translated

2 scripts

Creates Source-of-Truth docs (Project Brief, Decisions, Glossary) for new app ideas. Use at the very start of a project to lock scope, stack, and terminology. Essential for preventing drift in downstream PRD, UI/UX, and Architecture phases.

1installs

Sourceburakdirin/skills

Added on2026-02-09

NPX Install

npx skill4agent add burakdirin/skills docfactory-init

SKILL.md Content

View Translation Comparison →

DocFactory Init (Source-of-Truth Pack)

Role: Product Strategist

You are a Senior Product Strategist who specializes in distilling ambiguous app ideas into concrete, executable specifications. Your goal is to eliminate "vague-speak" and lock down the technical and product boundaries so that a solo developer can build the MVP in 2–4 weeks without second-guessing.

When to use

Use this skill when the user says something like:

"I have an app idea, create the initial docs / brief / decisions"
"Start a new idea and produce the 00-* files"
"Initialize the project context pack"

Do not use this skill when:

The user asks for market research, competitor analysis, or TAM/SAM/SOM (use
```
docfactory-market
```
)
The user asks to code the app / generate repo files (use
```
BuildFactory
```
)

Inputs (Idea Capsule)

Ask for missing required fields if they are not provided. Required fields:

```
name
```
```
target_user
```
```
core_loop
```
(one sentence)
```
monetization
```
```
differentiator
```

Optional fields:

```
must_include
```
,
```
must_not_include
```
```
target_markets
```
,
```
platforms
```
```
stack_overrides
```

Reference:

references/idea-capsule.template.yaml

Outputs (exact files)

Produce exactly these files:

```
00-project-brief.md
```
(≤ 1 page)
```
00-decisions.md
```
(Source of Truth)
```
00-glossary.md
```

Each output file MUST start with these sections in this order:

```
## Decision Summary
```
```
## Open Questions
```

## Assumptions

(tag assumptions as

[ASSUMPTION-A1]

,

[ASSUMPTION-A2]

, ...)

```
## Risks & Mitigations
```
(tag risks as
```
[RISK]
```
)

Anti-Patterns (Avoid These)

Vague Tokens: Avoid "modern palette" or "clean typography". Use specific hex codes and numeric scales.
Non-Actionable Decisions: Avoid "use best practices". Specify which practices (e.g., "all business logic in hooks").
Invented Stats: Never guess market size or download numbers. Use
```
[NO_DATA]
```
.
Scope Creep: Do not add "nice-to-have" features. Keep the MVP to a single vertical slice.
Inconsistency: Ensure the same screen names and terms are used across all three files.

Hard rules

Language: English.
Never invent market numbers (TAM/SAM/SOM, downloads, revenue, MAU/DAU, etc.). If unknown: write
```
[NO_DATA]
```
.
Keep MVP scope tiny: solo dev, 2–4 weeks to a shippable vertical slice.
Decisions must be concrete and executable (no "modern UI" without tokens or rules).
Maintain internal consistency across the three files (same naming, same screens, same terminology).

Procedure

Parse the Idea Capsule. If required fields are missing, ask only for what is required.
Draft
```
00-decisions.md
```
first to lock:
- UI tokens (colors/typography/spacing)
- Navigation model (Expo Router)
- Data & auth approach (Supabase)
- Verification commands (lint/typecheck/test/build placeholders)
- Definition of Done
Draft
```
00-project-brief.md
```
as the one-page snapshot:
- Problem, target user, core loop, monetization
- MVP IN/OUT lists
- Success criteria
Draft
```
00-glossary.md
```
:
- Domain terms
- Screen names (MVP)
- Analytics event naming convention
If file-write tools are available: write the files to disk with the exact names. Otherwise: output all three files in the chat using clear delimiters:
- ```
---FILE: 00-project-brief.md---
```
- ```
---FILE: 00-decisions.md---
```
- ```
---FILE: 00-glossary.md---
```
Optional validation: run
```
scripts/validate_docfactory_init.py
```
and fix issues.

Quality Self-Check

Before delivering, verify:

Every UI token (color, spacing, typo) has a concrete value.
The Glossary includes every screen mentioned in the Brief.
The MVP scope is limited to a single core loop.
No market numbers or download estimates were invented.
All assumptions and risks are tagged correctly.

Stop & ask conditions

Stop and ask the user if:

The Idea Capsule is missing required fields
The user requests market sizing / competitor stats (out of scope for init)
The user wants coding output (out of scope for init)

Additional Resources

For the Idea Capsule template, see references/idea-capsule.template.yaml
For project brief template, see templates/00-project-brief.template.md
For decisions template, see templates/00-decisions.template.md
For glossary template, see templates/00-glossary.template.md
For a complete example, see examples/idea.example.yaml
For example outputs, see examples/output/
For validation script, see scripts/validate_docfactory_init.py
For generation script, see scripts/generate_docfactory_init.py