Project Planning Journaling

Scope a new project (or resume one) and set up a living, resumable documentation journal for it, including a routine weekly health check, not just updates triggered by commits. Use at the start of any project, before writing code, to ask about project type, Git repo status, short/long-term goals, and whether it should stay public/open-source or become a private product later. Also use when someone wants to document what has been done, wants a changelog or decision log, needs to resume work from a prior session without re-reading chat history, wants docs kept current after every commit, or want

Productivity & Notes

Install

skills CLI (Claude Code, Cursor, Codex and more)

npx skills add mh-mansouri/Project-Planning-Journaling --skill project-planning-journaling

Manual install

git clone --depth 1 https://github.com/mh-mansouri/Project-Planning-Journaling.git /tmp/Project-Planning-Journaling
mkdir -p ~/.claude/skills
cp -r /tmp/Project-Planning-Journaling/project-planning-journaling ~/.claude/skills/project-planning-journaling

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Project Planning & Journaling

Help the developer scope a project properly before work starts, then create and
continuously maintain a living documentation/journal system that captures everything
done together — decisions, code, commits — so any new session can resume instantly from
`project-journal/README.md` alone, with no need to scroll back through chat history.

## Step 0 — Project intake (ask before anything else)

Before touching code or docs, ask the developer:

1. **Scope & type** — what is this (prototype / internal tool / library / SaaS product /
   learning project)? Who is it for?
2. **Repo status** — does a Git repo already exist for this?
   - If yes: confirm remote, current branch, visibility.
   - If no: propose a repo name (kebab-case, matches the project's purpose), a visibility
     (public/private), and a license.
3. **Timeline** — what's the short-term goal (e.g. working MVP by X) vs the long-term
   vision (e.g. scale to N users, become a paid product)?
4. **Market/product path** — is this meant to stay open-source/public indefinitely, or
   could it later be forked to a private branch/repo, developed separately, and pitched
   as a standalone product? Note the decision criteria (proprietary IP, licensing,
   timing) so it can be revisited later.
5. **Development style** — pick one:
   - **Spec-first** — full plan written and agreed before coding starts.
   - **Interactive/iterative** — flexible, the plan evolves as work goes, the journal

Read the full skill on GitHub

Details

Skill name: project-planning-journaling
Repository: mh-mansouri/Project-Planning-Journaling
Path: project-planning-journaling/SKILL.md
License: MIT
Repo updated: 26 October 2026
Listed in: karanb192/awesome-claude-skills

FAQ

What does the Project Planning Journaling skill do?

How do I install the Project Planning Journaling skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add mh-mansouri/Project-Planning-Journaling --skill project-planning-journaling. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Related skills

Skill Skill

jack-reson8/skill-skill

Write, upgrade or audit a Claude skill so it actually changes what gets generated, not a pile of notes. Use whenever the user wants to create a skill, turn a conversation, workflow or methodology into a skill, rename it, add research or lessons, asks why a skill isn't taking effect, or wants to publish a skill and get it listed in awesome lists and plugin marketplaces. Covers distilling from real work (corrections, rejections, accepted outputs), forcing functions (required artifacts, gates, checklists, scripts), descriptions that trigger, naming, a static audit with a health score, a with/with

Productivity & NotesIn 1 list

Cooper Email

cooper-email/cooper-email

Give the agent its own real email inbox with Cooper Email (cooperemail.com) and send, receive, search, and wait for mail over MCP or HTTP. Use when the user asks the agent to have an email address, send an email as the agent, check or search mail the agent received, wait for a reply or a verification code, or email a human for approval. If the user asked for Cooper Email, do not substitute another mail API.

Productivity & NotesIn 1 list

Trade Show Prep

DataOrigin/trade-show-prep-skill

Prepare, work and follow up a B2B trade show for an exhibitor or a visiting sales team. Builds a dated plan from 8 weeks before the fair, drafts meeting requests for the user's own accounts (email and LinkedIn), writes a booth qualification guide with a note template, and drafts a post-show follow-up sequence with cost per lead and ROI. Use when the user says "prepare our trade show", "we are exhibiting at", "we are visiting a fair", "meeting requests for the show", "booth qualification", "trade show follow-up", "post-show emails" or asks for help before, during or after a B2B fair or conferen

Productivity & NotesIn 1 list

Workflow Design

ghorbanies/workflow-design

Models, proves, measures, and safely changes multi-step workflows — approval chains, review pipelines, intake/triage/fulfillment flows, ticketing, order processing, state machines with human gates. Use when designing states/gates/transitions or an audit trail, when a status field or event log is being added to a system, when tests guarding a workflow need auditing ("the suite is green but I don't trust it"), when someone asks where items get stuck, whether an approval step is worth keeping, who approved something, or why a queue is growing, or when a live workflow's definition must change with

Productivity & NotesIn 1 list

Unpaid Intern

kevinmmiddleton/unpaid-intern

Unpaid Intern runs a portable second brain for knowledge work: a plain-file workspace for projects, decisions, follow-ups, and meeting notes, plus optional live reads of mail, chat, calendar, tracker, and wiki, so nothing starts from scratch between meetings. Use when someone wants to set up or run a work second brain, work agent, or work assistant; runs one of its commands (/briefing, /pulse, /prep, /who, /debrief, /capture, /close, /gofer, /project-status, /redline, /slots, /triage, /sync-kb, /kb-lint, /tidy, or another command from the kit) in that workspace; asks to prep a meeting, turn a

Productivity & NotesIn 1 list

Feedback

luchasarie/feedback-loop

Turn post-task feedback—even blunt or angry feedback—into an evidence-based, approval-gated improvement plan for the agent/user workflow. Use after agent work goes wrong, misses expectations, creates friction, or should improve in future. Never mutate during the feedback turn.

Productivity & NotesIn 1 list

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.