dull-bird/deeporbit · Archived

do.kickoff

Convert an idea or Inbox note into a structured DeepOrbit project. Use when the user wants to start, scope, or turn an idea into a project with a reviewable plan and C.A.P. project note.

First seen Apr 26, 2026

Installation

$ npx skills add dull-bird/deeporbit --skill do.kickoff

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from dull-bird/deeporbit · top by installs.

npx skills add dull-bird/deeporbit

Browse all from dull-bird/deeporbit

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 5
License LICENSE
Default branch master
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,388 B
  • docs SUMMARY.md 204 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 6 installs

SKILL.md

Kick Off a Project

Keep the workflow portable. Use the current runtime's native Goal or Tracker when it exists, but keep the Markdown plan as the durable source of truth. Do not require subagents or an external self-invoking loop.

1. Resolve input and context

Accept an Inbox path, inline idea, or—when no input is given—offer the notes in 00_Inbox/. Read deeporbit.json for paths and language. Search related context with:

deeporbit --vault "<vault-path>" rag "<project subject>"

If semantic search is unavailable, use deeporbit ... rag --lexical-only or the runtime's file search. Identify overlapping projects before creating a duplicate.

2. Write a reviewable plan

Create 90Plans/PlanYYYY-MM-DDKickoff<ProjectName>.md containing:

  • source and one-sentence goal;
  • related notes/projects and a merge recommendation when overlap is high;
  • Area, estimated scale, constraints, phases, and success criteria;
  • only the clarification questions that materially affect execution.

Open it with do.obsidian-open when available. Ask for confirmation before turning the plan into a project note because this step can reorganize the user's Inbox.

3. Execute the confirmed plan

Create 20Projects/<ProjectName>.md for a small project or 20Projects/<ProjectName>/<ProjectName>.md for a larger one. Use frontmatter:

---
title: Project Name
type: project
created: YYYY-MM-DD
status: active
area: "[[AreaName]]"
due:
priority: P2
tags: [project]
---

Use C.A.P. sections: Context, Actions, and Progress. Link it from today's Daily Note. Move the completed plan to 90Plans/Archive/. For an Inbox source, set status: processed and archived: YYYY-MM-DD, then move it to 99System/Archive/Inbox/YYYY/MM/ without overwriting an existing file.

  • Set author: ai in frontmatter for every note you create; switch to author: mixed when substantially rewriting a human-authored note. Authorship lives in frontmatter only — never add visible badges.

Report created and moved paths plus the next concrete action. Opening a note through Obsidian is useful but never a condition for success.