new-obsidian-project

Interview users to generate schema-aligned Obsidian project note trees.

Updated Jul 11, 2022
One-click install
npx skills add https://github.com/zhengfran/dotconfig --skill new-obsidian-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-obsidian-project
Source: https://github.com/zhengfran/dotconfig/tree/main/tools/ai/agents/skills/new-obsidian-project
Command: npx skills add https://github.com/zhengfran/dotconfig --skill new-obsidian-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents vague, half-formed project ideas from turning into messy notes by forcing an interview that resolves scope, constraints, risks, approach, and success criteria before generating a structured Obsidian dashboard.

Core Features & Use Cases

  • Relentless round-by-round interviewing to resolve every branch of the project decision tree one question at a time, including recommended answers and adaptive depth by project size.
  • Vault-grounded planning that checks for relevant past projects in your vault to reuse patterns instead of starting from scratch.
  • Automatic Obsidian note-tree creation for greenfield (Project + Epics + Tasks) or retrospective (Project + Supplements) with the vault’s PARA-style schema and correct parent/project rollups.

Quick Start

Tell the AI: “/new-obsidian-project I want to build a tool that turns my meeting notes into action items, and I already have some notes in my vault,” and it will grill you question-by-question, then create the full Obsidian project tree in the right space.

Frequently Asked Questions about new-obsidian-project

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break down a project idea into Obsidian notes for epics and tasks?

To break down a project idea into Obsidian notes, this Skill interviews you one question at a time to resolve scope and risks, then generates a structured Project, Epic, and Task note tree directly in your vault.

What is the best way to plan a greenfield project in Obsidian using kanban and agile principles?

The best way to plan a greenfield project in Obsidian is through a structured interview that establishes scope and success criteria, outputting a schema-aligned set of Project, Epic, and Task notes to populate your kanban board.

Can I generate an Obsidian project tree from an existing codebase path?

Yes, you can generate an Obsidian project tree from an existing codebase path. The Skill supports retrospective documentation by creating Project and Supplement notes based on your codebase structure and vault schema.

How do I ensure my generated Obsidian project notes conform to my vault's PARA-style schema?

To ensure generated project notes conform to your vault's PARA-style schema, the Skill clones per-project base templates and enforces strict metadata conformity for Type, Phase, Status, Priority, Parent, and Project attributes.

Does this Obsidian project planning tool reuse patterns from past projects in my vault?

Yes, this Obsidian project planning tool checks your vault for relevant past projects. It grounds the planning process by reusing established patterns instead of starting your new project breakdown from scratch.

Why should I use a one-question-at-a-time interview for project breakdown instead of generating all notes at once?

You should use a one-question-at-a-time interview for project breakdown to prevent vague ideas from creating messy notes. Relentless round-by-round resolution ensures complete scope, constraints, and risks are defined before generating the full dashboard.