Skip to content
Skills Library
Management & product · Planning

do.kickoff

/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.

Repository
deeporbit ↗
Licence
MIT
Last repository change
08.10.2026

Assessment and security

95/ 100Class: good
Format20 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 08.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Original author description

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.

How it works

  1. 1. Resolve input and context
  2. 2. Write a reviewable plan
  3. 3. Execute the confirmed plan
Original SKILL.md headings · 58 lines, 302 words
SKILL.md preview
---
name: do.kickoff
description: 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.
---

# 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:

```bash
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 `90_Plans/Plan_YYYY-MM-DD_Kickoff_<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 `20_Projects/<ProjectName>.md` for a small project or
`20_Projects/<ProjectName>/<ProjectName>.md` for a larger one. Use frontmatter:

```yaml
---
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 `90_Plans/Archive/`. For an Inbox source, set
`status: processed` and `archived: YYYY-MM-DD`, then move it to
`99_System/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.

Versions

The database has no other skills named do.kickoff.

Database snapshot: 13.11.2026 · package version 1bd37cce45fa (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90artifact-template-project-kickoff
    Create a presentation using the Project Kickoff template and its retained reference file. Use when the user selects or names Project Kickoff. Align teams on project goals, scope, roles, milestones, risks, and the working model.
  • 100project-brief
    Writes a one-page home note for a project covering why, goal and definition of done, scope and non-goals, milestones, people, risks, and links. Use when someone is starting a project, needs a project one-pager, kickoff doc, or charter, or has a project scattered across messages…
  • 95do.research
    Plan and execute checkpointed deep research for technologies, concepts, papers, or complex questions. Use when the user asks for deep research, a literature review, evidence synthesis, or a durable research note in their DeepOrbit vault.
  • 86kickoff
    Use when the challenge brief just arrived or the team has no plan yet — turns the brief into one chosen idea, a minimal architecture, task split, and docs/PLAN.md within ~45 minutes.
  • 90kickoff
    Stage 0 of pitwall. Starts a new project from a one-line idea - asks about it one question at a time, proposes a process level, lays out the project template, writes docs/IDEA.md, sets up merge protection on GitHub and asks whether low and normal risk PRs may merge without the…
  • 91do.init
    Initialize or safely upgrade a DeepOrbit Obsidian vault. Use when the user asks to set up DeepOrbit, create the vault folders, migrate legacy Chinese folder names, repair a partial installation, or generate deeporbit.json.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.