personal-os

Plugin personal-os from marketplace personal-os-marketplace in ygavrilov/plugin-personal-os. Commands read from the repo's manifest — 1 month ago.

Skills (21)

• notes-classification

  Knowledge skill — half-life heuristic for classifying daily notes content into wiki, weekly artifacts, both, or drop.

• wiki-ingest

  Knowledge skill — rules and standards for ingesting a source file into the wiki. Covers page types, frontmatter, mandatory index and log updates.

• wiki-query

  Knowledge skill — rules for querying the wiki to answer a question. Covers index navigation, page reading, synthesis, and filing non-trivial answers as new pages.

• research

  SOP to run verified, on-demand research on any question and write a structured research report to research/. Adapted from the ICOR "Pax" research-agent protocol — triangulate sources, mark confidence, lead with the actionable answer. Use when a worker or PA is asked to research, investigate, fact-ch

• setup-skill-permissions

  Scan every project skill's allowed-tools frontmatter and write a merged, deduplicated, sorted allowlist into the project .claude/settings.json, so all skill tool permissions are enabled by default with no per-session prompts. Use when the user says "setup skill permissions", "regenerate permissions"

• sop-dev-architecture

  SOP to design a technical solution and produce an Architecture Decision Document (ADD) — context review, options analysis (2-3 approaches with trade-offs), per-layer deep-dive (DB / backend / frontend / infra / SEO), risks, and decision. Use when a worker is delegated a dev architecture task, or ask

• sop-dev-implement

  SOP to implement a single Work Breakdown task / vertical slice against a repo — read context, locate the code, make the change following the project's existing conventions, run the build/tests locally, and update PROGRESS.md. Use when a worker is delegated a dev implementation task, or asked to "imp

• sop-dev-ingest-repo

  SOP to onboard an existing codebase into personal-os — analyze a repo across technology / architecture / standards / state and produce a populated PROJECT_CONTEXT.md in the target project's .claude/. Use when a worker is delegated a dev task against a project that has no PROJECT_CONTEXT.md yet, or a

• sop-dev-requirements

  SOP to turn a plain-language dev request into a structured requirements document (PRD for user-facing features, RFD for technical changes) via a structured interview, stakeholder mapping, and process analysis. Use when a worker is delegated a dev requirements task, or asked to "gather requirements",

• sop-dev-test

  SOP to QA an implemented feature — map acceptance criteria to code, run the existing test suite, write missing tests, validate behavior, record defects, and produce a PASS/FAIL test report. Use when a worker is delegated a dev QA task, or asked to "test this feature", "run QA", "write the test repor

• sop-dev-work-breakdown

  SOP to break approved scope into an executable Work Breakdown Document — a Foundation block plus Feature vertical slices (DB to API to UI), with task owners, blocked-by/blocks dependencies, critical path, and a parallelism map. Use when a worker is delegated a dev planning task, or asked to "break d

• sop-draft-reply

  SOP to write a reply draft (email or message) to a file in drafts/. Never sends. Use when a worker is delegated a REPLY task from workflow-process-message.

• sop-plan

  SOP that owns the full personal-os planning and review lifecycle. One skill, four sub-procedures the invoker selects at runtime: WEEKLY-REVIEW (retrospect the week, score against the framework, write weeks/W[N]-[YEAR]-review.md, then plan next week + create calendar events), WEEKLY-PLAN (standalone

• sop-schedule

  SOP for scheduling a task onto the calendar. Finds a free slot respecting the user's configured work-rhythm and daily-slot rules, then creates the event. Degrades gracefully when no calendar MCP is present. Use when a worker is delegated a SCHEDULE task.

• sop-task

  SOP for the full task lifecycle in personal-os — from capture through executing a tracked task to close. Sub-procedures the invoker selects at runtime: CAPTURE (append a one-liner to inbox.md), CREATE (make a tracked task file from template, score it via the framework), UPDATE (move status / block /

• sop-wiki

  SOP for the full personal-os wiki lifecycle — store durable knowledge, retrieve related projects/ideas/concepts, or check consistency. Self-contained — owns all mechanics (bootstrap, page creation, index, log, cross-links, synthesis) directly; no delegation to a separate skill. Use when a worker is

• workflow-deliver-feature

  PA orchestrator for end-to-end software delivery. Runs a feature/project through the SDLC by fanning out to workers running the sop-dev-* leaf SOPs in critical-path order — ingest-repo → requirements → architecture → work-breakdown → implement (per slice) → test. PA owns all fan-out and the gate bet

• workflow-ingest-notes

  Orchestrator that reads raw daily notes, classifies content by half-life, then dispatches workers to run sop-wiki (ingest) for durable knowledge and sop-plan/sop-task for weekly artifact updates — including extracting quarterly-relevant items into the current week's review/plan files. Auto-ingest is

• workflow-process-message

  PA message processing protocol. Classify any incoming message into actions, route all branches in parallel. Use when processing any message, note, request, or input that needs to be acted on, stored, scheduled, or replied to.

• workflow-setup-os

  First-run (and re-run) setup wizard for Personal OS. Detects missing or partial config in the workspace CLAUDE.md ## Config section, runs a grouped interview (identity, work rhythm, optional daily slots, calendars + mcp_ical y/n), writes the answers into the Config section in place, copies framework

• workflow-triage-tasks

  PA task triage. Review open tasks, (re)score against the framework, decide route per task (schedule / execute / defer / drop), delegate each to a worker. Use when user says "triage tasks", "what should I work on", "review my tasks".

Subagents (4)

• junior-worker

  Junior Worker — fast low-cost executor. Process-agnostic. Executes a single delegated task by invoking the relevant SOP skill. Use for simple, well-defined, low-stakes tasks. Spawned by PA, never self-directed.

• lead-worker

  Lead Worker — highest-capability executor. Process-agnostic. Executes a single delegated task by invoking the relevant SOP skill. Use for complex or high-stakes tasks requiring strongest reasoning. Spawned by PA, never self-directed.

• pa

  Personal Assistant — single point of contact for all inputs. Receives any message, classifies it, and routes to the correct handler (calendar, wiki, inbox, drafts, or direct execution). Use proactively for any input that needs to be processed, scheduled, captured, stored, or replied to.

• senior-worker

  Senior Worker — mid-capability executor. Process-agnostic. Executes a single delegated task by invoking the relevant SOP skill. Use for standard tasks of moderate complexity. Spawned by PA, never self-directed.

Hooks (1)

• UserPromptSubmit

  node "${CLAUDE_PLUGIN_ROOT}/hooks/enforce-workflow.js"

Similar plugins