← all plugins

1. ▌
   event-log · projectious-work bundle

   Append-only event log — the probabilistic record of everything that happened in the project. Use whenever something notable happens that the project should remember — work items created/transitioned, decisions recorded, bindings changed, incidents occurred, releases shipped.
   0
   repo stars
2. ▌
   release-semver · projectious-work bundle

   Semantic versioning releases — version bumps, changelogs, tags, publishing. Use when preparing a new release: deciding the version bump, drafting the changelog, tagging the commit, and publishing to the project's distribution channel.
   0
   repo stars
3. ▌
   agent-card · projectious-work bundle

   Project processkit agent-card Artifacts into canonical public agent-card JSON files. Use when publishing an agent identity, endpoint, capability, or interoperability card from repository context into a runtime-visible file.
   0
   repo stars
4. ▌
   skill-gate · projectious-work bundle

   Session-start meta-skill that enforces the 1% rule: before any action on a processkit entity or context/ file, if there is even a 1% chance a processkit skill applies, you MUST check skill-finder first. Load this skill at the start of every session that may involve processkit work. Use when beginning a new task, when unsure which skill applies, or when you are about to edit context/, create an entity, or run an MCP tool.
   0
   repo stars
5. ▌
   repo-management · projectious-work bundle

   Reconcile repository issues, pull requests, merge requests, local git state, commits, and pushes across GitHub, GitLab, Gitea, Forgejo, Codeberg, Bitbucket, Azure DevOps, and SourceHut.
   0
   repo stars
6. ▌
   task-router · projectious-work bundle

   Route a task description to the right processkit skill, project-specific process override, and MCP tool in a single deterministic call — use this at the start of every processkit domain task.
   0
   repo stars
7. ▌
   skill-finder · projectious-work bundle

   Navigation aid for the processkit skill catalog — maps natural-language cues and task types to the right skill. Read this when you are unsure which skill applies to the current task, when the user names a task without naming a skill, or at session start when orienting to an unfamiliar project. Always the first skill to consult; never the last.
   0
   repo stars
8. ▌
   team-creator · projectious-work bundle

   Compose a provider-neutral AI team by tiering accessible models on cost-efficiency, capability, latency, and governance, then mapping the 8 processkit role archetypes onto catalog Roles + RoleSlots inside a chartering Scope. Use when bootstrapping a new project team, rotating after a provider change, or quarterly rebalancing. Triggers: "create my AI team", "compose a team", "rebalance the team", "review the team".
   0
   repo stars
9. ▌
   team-manager · projectious-work bundle

   Create and maintain TeamMember entities — humans and named AI personas that participate in the project with persistent identity, personality, and tiered memory. Use when adding a new persistent team-member (human or named AI), managing the name pool, scaffolding memory trees, or exporting/importing a team-member bundle. Replaces the deprecated actor-profile skill (DEC-20260422_0233-SpryTulip).
   0
   repo stars
10. ▌
    actor-profile · projectious-work bundle

    Create and maintain Actor entities — humans and AI agents that participate in the project. Use when adding a new collaborator (human or agent) to the project, updating their preferences/expertise, or querying who does what.
    0
    repo stars
11. ▌
    aggregate-mcp · projectious-work bundle

    Expose the processkit MCP tool surface through a single stdio server. Use for harnesses that eagerly start every configured MCP server, such as Codex, while keeping per-skill MCP servers available.
    0
    repo stars
12. ▌
    id-management · projectious-work bundle

    Generate unique entity IDs following the project's configured format. The write-side foundation that every entity-creating skill depends on. Use whenever a new entity is being created and needs an ID, or when validating an ID format, or to inspect the project's ID configuration.
    0
    repo stars
13. ▌
    release-audit · projectious-work bundle

    Detect-only pre-release validation sweep over the processkit content tree. Walks entity files, SKILL.md definitions, MCP server tools, and cross-references, then emits a single human-readable report with ERROR / WARN / INFO counts. Use when the user invokes `/pk-release-audit`, before tagging a release, or any time you need a comprehensive structural health check beyond what pk-doctor covers. Detect-only; never modifies any file under `context/`.
    0
    repo stars
14. ▌
    retrospective · projectious-work bundle

    Generates a post-release blameless retrospective from project signals — synthesizing DORA-like metrics, WorkItem outcomes, session timeline, and drift deltas into a structured Artifact + LogEntry. Use at the end of a release cycle when asked to run a retro, "post-release review", "retrospective", or "post-mortem".
    0
    repo stars
15. ▌
    runtime-prune · projectious-work bundle

    Inspect, plan, and invoke safe cleanup for runtime-manager-owned state without binding the workflow to a specific host orchestrator or agent provider.
    0
    repo stars
16. ▌
    skill-builder · projectious-work bundle

    Author a new processkit skill end-to-end — use-case interview, frontmatter, body sections, Gotchas, and trigger-phrase generation.
    0
    repo stars
17. ▌
    skill-reviewer · projectious-work bundle

    Audit an existing processkit skill against the 5 Skill Killers, the Agent Skills standard, and Anthropic's troubleshooting playbook, producing a categorized findings report and draft Gotchas.
    0
    repo stars
18. ▌
    decision-record · projectious-work bundle

    Record decisions with rationale, alternatives, and consequences — the ADR pattern as a primitive. Use when a consequential choice is made — architecture, tooling, process, scope, trade-off. Capture WHY, not just WHAT.
    0
    repo stars
19. ▌
    gate-management · projectious-work bundle

    Manage Gate entities — validation checkpoints that WorkItems, scopes, or policy applications must pass (code review, security scan, tests). Use when defining or updating a checkpoint for v2 workflow surfaces — code review, tests green, security scan, stakeholder approval.
    0
    repo stars
20. ▌
    note-management · projectious-work bundle

    Captures, reviews, and promotes Note entities — the lightweight knowledge capture primitive in processkit. Notes are quick-capture units (thoughts, insights, questions, references) that are reviewed periodically and promoted to WorkItems, DecisionRecords, or other primitives when they ripen. Use when the user says "remember this", "note that", "I had an idea", or when running a periodic note review session.
    0
    repo stars
21. ▌
    owner-profiling · projectious-work bundle

    Build and maintain a structured personal-context portfolio for the project owner — identity, working style, goals, team, decision patterns. Includes both an interview protocol for bootstrapping and observable-signal patterns for incremental refinement. Use to bootstrap an owner profile (interview), to refine an existing profile (target one file), or to incrementally update the profile based on observed patterns from a normal session (the agent watches for signals and proposes additions when evidence accrues).
    0
    repo stars
22. ▌
    role-management · projectious-work bundle

    Create and maintain Role entities — named sets of responsibilities that actors can fill. Use when defining a new role in the project (developer, reviewer, tech-lead, release-manager) or updating an existing role's responsibilities.
    0
    repo stars
23. ▌
    standup-context · projectious-work bundle

    Writes a structured standup update as a session.standup LogEntry — capturing what was done, what is in progress, what comes next, and any blockers. Use when the user says "write a standup", "standup update", "what did I do today", "write a status update for the team", or at the end of a session on projects that run daily standups.
    0
    repo stars
24. ▌
    status-briefing · projectious-work bundle

    Generates a concise status briefing after session-start reconciliation — synthesizing current state, open decisions, key risks, and today's priority actions. Use at session start, for "pk-resume", a briefing, catch-up, or today's focus.
    0
    repo stars
25. ▌
    agent-management · projectious-work bundle

    Orchestrate multi-agent workflows with task decomposition, role assignment, handoff protocols, and per-session context budgeting.
    0
    repo stars
26. ▌
    context-grooming · projectious-work bundle

    Review and prune the project context — archive completed work, summarize stale entries, and propose disabling unused skills.
    0
    repo stars
27. ▌
    index-management · projectious-work bundle

    SQLite-backed index over all entity files in the project. The read-side foundation for every other MCP server. Use whenever an agent needs to look up entities by ID, kind, state, or text — instead of grepping the filesystem.
    0
    repo stars
28. ▌
    scope-management · projectious-work bundle

    Manage Scope entities — bounded containers grouping related work (sprint, milestone, project, quarter). Use when creating or updating a grouping boundary — sprint, milestone, quarter, project, release — that other entities will reference.
    0
    repo stars
29. ▌
    session-handover · projectious-work bundle

    Write an end-of-session handover LogEntry capturing current state, open threads, next action, and git context for session continuity.
    0
    repo stars
30. ▌
    context-archiving · projectious-work bundle

    Plan and execute hot-to-cold processkit context archiving while keeping archived entity metadata queryable through the shared index.
    0
    repo stars
31. ▌
    model-recommender · projectious-work bundle

    Recommend the right AI model for a task by scoring candidates across six dimensions (Reasoning, Engineering, Speed, Breadth, Reliability, Governance) and displaying a spider-chart profile.
    0
    repo stars
32. ▌
    binding-management · projectious-work bundle

    Manage Binding entities — scoped, temporal, many-to-many relationships between v2 entity surfaces. Use when a relationship needs scope, time, or its own attributes — e.g. 'Alice is the tech lead for project X from Jan to June' or 'the security gate applies to this release WorkItem only on the main branch'.
    0
    repo stars
33. ▌
    process-management · projectious-work bundle

    Legacy/migration guidance for v1 Process entities — declarative workflow definitions with roles, gates, and a definition of done. In v2, use process-instance WorkItems plus Artifact-backed definitions instead of creating new Process records.
    0
    repo stars
34. ▌
    processkit-gateway · projectious-work bundle

    Provider-neutral processkit MCP gateway. Use when a harness should see one processkit MCP surface while processkit keeps per-skill servers canonical and available.
    0
    repo stars
35. ▌
    supply-chain-audit · projectious-work bundle

    Discover supply-chain manifests, run structured supply-chain audits, and export SBOMs through a dedicated MCP surface.
    0
    repo stars
36. ▌
    artifact-management · projectious-work bundle

    Create, retrieve, query, and update Artifacts — tangible deliverables produced by the project. Use when storing or retrieving documents, designs, datasets, build outputs, slide decks, or any completed deliverable that should be registered in the project catalog.
    0
    repo stars
37. ▌
    category-management · projectious-work bundle

    Manage Category entities — taxonomies and classification schemes that group other entities by type, area, tier, etc. Use when defining a new classification axis (priority levels, bug severity, feature tier, product area) that other entities will be tagged with.
    0
    repo stars
38. ▌
    eval-gate-authoring · projectious-work bundle

    Turn observed run outputs into eval-spec Artifacts, paired Gates, and policy bindings. Use when creating or calibrating automated, human, or LLM-as-judge eval gates for processkit workflows.
    0
    repo stars
39. ▌
    schedule-management · projectious-work bundle

    Legacy/migration guidance for v1 Schedule entities. In v2, define recurring cadences as Binding(type=time-window) records with recurrence conditions instead of creating new Schedule records.
    0
    repo stars
40. ▌
    workitem-management · projectious-work bundle

    Create, transition, query, and link WorkItems — tasks, stories, bugs, epics. Use when the user asks to add, update, query, or link work items — backlog items, tasks, bugs, user stories, or epics.
    0
    repo stars
41. ▌
    migration-management · projectious-work bundle

    Manage Migration entities — pending, in-progress, and applied transitions between upstream source versions. Use when an upstream source bumps version (processkit, a host installer, or a community package), when a user wants to draft a migration plan, when an agent needs to reason about pending migrations, or when working through an in-progress migration.
    0
    repo stars
42. ▌
    security-projections · projectious-work bundle

    Project processkit security policy Artifacts into runtime policy files for Agent-IDS and Tetragon-style enforcement. Use when an agent-ids-rule or image-provenance-policy Artifact must become an executable security configuration.
    0
    repo stars
43. ▌
    status-update-writer · projectious-work bundle

    Generates clear, structured status updates for stakeholders — from project context, backlog state, or a brief description of recent work. Use when asked to write a status update, weekly report, progress summary, or team briefing about a project or initiative.
    0
    repo stars
44. ▌
    constraint-management · projectious-work bundle

    Manage Constraint entities — rules and limits the project must respect (budget, latency SLO, team size, compliance). Use when recording a rule, limit, or boundary that affects decisions — budget ceiling, latency SLO, regulatory requirement, team bandwidth.
    0
    repo stars
45. ▌
    discussion-management · projectious-work bundle

    Manage Discussion entities — structured, multi-turn conversations that explore questions and produce decisions. Use when a question or design choice needs multi-turn exploration before a decision is reached — RFCs, design debates, trade-off analyses.
    0
    repo stars
46. ▌
    research-with-confidence · projectious-work bundle

    Investigates a question systematically before answering — verifying claims through sources, distinguishing known facts from inferences, and calibrating expressed confidence to actual certainty. Use when asked to research a topic, verify a claim, evaluate a technology, or answer a question where accuracy matters more than speed.
    0
    repo stars
47. ▌
    project-reconciliation · projectious-work bundle

    Reconcile a processkit project’s migrations, health findings, and repository collaboration queue. Use when resolving all migrations, pk-doctor findings, GitHub issues, pull requests, or release blockers.
    0
    repo stars
48. ▌
    state-machine-management · projectious-work bundle

    Legacy/migration guidance for v1 StateMachine entities. In v2, lifecycle rules are implementation contracts owned by MCP servers, not first-class records to create during normal project work.
    0
    repo stars
49. ▌
    cross-reference-management · projectious-work bundle

    Conventions and helpers for lightweight relationships between entities expressed as frontmatter references (not first-class Binding entities). Use when linking two entities with a simple, unscoped, untemporal relationship — 'this work item blocks that one', 'this decision relates to that work item'. For scoped/temporal relationships, use binding-management instead.
    0
    repo stars
50. ▌
    excalidraw · projectious-work bundle

    Generates Excalidraw diagrams programmatically as hand-drawn-style JSON. Use when creating architecture diagrams, flowcharts, or hand-drawn-style visuals for documentation, or when converting existing diagrams to editable Excalidraw JSON.
    0
    repo stars
51. ▌
    logo-design · projectious-work bundle

    Creates SVG logos with scalable geometry, color theory, and variant generation. Use when designing logos, icons, or brand marks, generating favicons or social avatars, or reviewing a logo for scalability, color, or variant coverage.
    0
    repo stars
52. ▌
    ci-cd-setup · projectious-work

    CI/CD pipeline setup — GitHub Actions, testing, linting, deployment. Use when setting up CI from scratch, adding GitHub Actions, automating tests, wiring up deployment, or improving an existing build pipeline.
    0
    repo stars
53. ▌
    ml-pipeline · projectious-work bundle

    ML pipeline design — data versioning, experiment tracking, deployment patterns, drift monitoring. Use when building an ML pipeline from data to deployment, setting up MLOps tooling (DVC, MLflow, model registry), choosing deployment patterns (shadow, canary, A/B), or designing monitoring for drift and degradation.
    0
    repo stars
54. ▌
    prd-writing · projectious-work

    Write a Product Requirements Document structured with problem statement, goals, user stories, scope, and success metrics.
    0
    repo stars
55. ▌
    data-quality · projectious-work

    Data quality framework — completeness, accuracy, consistency, validation, and contracts. Use when implementing data validation, setting up quality checks for a pipeline, defining data contracts between teams, or investigating data anomalies.
    0
    repo stars
56. ▌
    data-science · projectious-work bundle

    Data analysis workflow from import through modeling and communication. Use when analyzing a dataset, exploring data, building a statistical model, selecting features, or communicating findings to stakeholders.
    0
    repo stars
57. ▌
    tailwind · projectious-work bundle

    Tailwind CSS v4 — utility-first styling, responsive design, dark mode, and component extraction. Use when building or reviewing Tailwind-based UIs, setting up Tailwind v4, or designing responsive or dark-mode styling.
    0
    repo stars
58. ▌
    legal-review · projectious-work

    Structures a systematic legal and compliance review of contracts, policies, or technical decisions — identifying key clauses, risks, and questions for counsel. Use when asked to review a contract, check compliance implications, flag legal risks in a technical design, or prepare for a legal consultation. Always surfaces work for qualified counsel; never replaces legal advice.
    0
    repo stars
59. ▌
    data-pipeline · projectious-work

    Data pipeline patterns — ETL/ELT, batch vs streaming, idempotency, orchestration. Use when designing a data pipeline, choosing between batch and streaming, implementing ingestion or transformation, setting up orchestration, or debugging pipeline failures.
    0
    repo stars
60. ▌
    pandas-polars · projectious-work bundle

    DataFrame operations with pandas and polars — groupby, joins, reshaping, performance. Use when manipulating tabular data, choosing between pandas and polars, optimizing DataFrame code, or translating between the two libraries.
    0
    repo stars
61. ▌
    dns-networking · projectious-work bundle

    DNS records, IP addressing, subnetting, common protocols, and diagnostic tools. Use when configuring DNS records, debugging resolution or connectivity, planning subnets, analyzing HTTPS/TLS errors, or diagnosing latency and routing issues.
    0
    repo stars
62. ▌
    changelog · projectious-work

    Generates and maintains CHANGELOG.md files following Keep a Changelog conventions — from git history, commit messages, or a description of changes. Use when asked to write a changelog, update release notes, or document what changed in a version.
    0
    repo stars
63. ▌
    debugging · projectious-work

    Systematic debugging — reproduce, read the error, isolate, hypothesize, fix, verify, document. Use when tracking down a bug, unexpected behavior, or test failure — including phrases like "this doesn't work", "why is this failing", or "help me debug".
    0
    repo stars
64. ▌
    documentation · projectious-work

    Writing effective project documentation — READMEs, API doc comments, and inline comments that explain why. Use when writing or improving documentation — READMEs, doc comments, inline comments, or when code lacks explanation for non-obvious behavior.
    0
    repo stars
65. ▌
    email-drafter · projectious-work

    Drafts clear, professional emails ready to copy and paste — from a brief description of the situation, audience, and intent. Use when asked to write, draft, or compose an email, reply to a message, or suggest how to phrase something professionally.
    0
    repo stars
66. ▌
    user-research · projectious-work

    Structures user research — planning sessions, synthesizing findings, and translating insights into product decisions. Use when planning user interviews, analyzing research data, creating personas or journey maps, or turning qualitative feedback into structured recommendations.
    0
    repo stars
67. ▌
    llm-evaluation · projectious-work

    LLM output evaluation — automated metrics, LLM-as-judge, A/B testing, regression testing. Use when measuring LLM output quality, comparing prompt or model versions, building an automated eval pipeline, setting up regression tests for prompt changes, or evaluating RAG systems and bias/safety.
    0
    repo stars
68. ▌
    frontend-design · projectious-work bundle

    Frontend architecture and UI design — component hierarchies, accessibility, performance, state management. Use when designing frontend architecture, building component hierarchies, making something accessible, optimizing Core Web Vitals, or choosing a state management approach.
    0
    repo stars
69. ▌
    alerting-oncall · projectious-work

    Alert design and on-call practices — severity, runbooks, SLO burn-rate alerting, escalation. Use when designing alerts, writing runbooks, reducing alert fatigue, setting up escalation policies, implementing SLO-based alerting, or improving on-call processes.
    0
    repo stars
70. ▌
    infographics · projectious-work bundle

    Creates data-driven infographics and charts as accessible SVG. Use when visualizing data, choosing a chart type, generating an SVG chart or infographic, or reviewing a visualization for clarity and accuracy.
    0
    repo stars
71. ▌
    pdf-workflow · projectious-work

    Generating and manipulating PDF files — from HTML, DOCX, or raw content using reportlab, weasyprint, or pypdf. Use when producing PDF reports, invoices, certificates, or when merging, splitting, or extracting text from existing PDFs.
    0
    repo stars
72. ▌
    api-design · projectious-work bundle

    REST API design — resource naming, HTTP methods, status codes, pagination, versioning, OpenAPI. Use when designing a new REST API, reviewing API contracts, writing OpenAPI/Swagger documentation, or choosing pagination, versioning, or error-format strategies.
    0
    repo stars
73. ▌
    ai-fundamentals · projectious-work bundle

    Explain and apply core ML/AI concepts — model types, training pipelines, evaluation metrics, and neural architectures.
    0
    repo stars
74. ▌
    rag-engineering · projectious-work bundle

    Retrieval-Augmented Generation pipelines — ingestion, chunking, embedding, vector stores, retrieval, evaluation. Use when building a RAG pipeline, choosing chunking strategies or embedding models, debugging retrieval quality or hallucinations, evaluating an existing RAG system, or scaling/migrating vector stores.
    0
    repo stars
75. ▌
    seo-optimization · projectious-work bundle

    SEO — on-page, technical, structured data, Core Web Vitals, and mobile-first indexing. Use when optimizing a website for search engines, adding meta tags or structured data, fixing Core Web Vitals, or auditing technical SEO.
    0
    repo stars
76. ▌
    logging-strategy · projectious-work bundle

    Structured logging strategy — levels, correlation IDs, context propagation, PII avoidance. Use when designing a logging approach, reviewing log statements, setting up log aggregation (ELK, Loki, CloudWatch), adding correlation IDs to a distributed system, or deciding what to log and what to keep out.
    0
    repo stars
77. ▌
    terraform-basics · projectious-work

    Infrastructure-as-code with Terraform/OpenTofu — resources, state, modules, plan/apply. Use when writing `.tf` files, managing cloud infrastructure with Terraform or OpenTofu, handling state and backends, or reviewing IaC code.
    0
    repo stars
78. ▌
    xlsx-modeling · projectious-work

    Creating Excel spreadsheets programmatically with openpyxl — worksheets, data, formulas, charts, formatting, and named ranges. Use when generating financial models, data reports, dashboards, or any structured spreadsheet from data or templates.
    0
    repo stars
79. ▌
    code-review · projectious-work

    Structured code review with a checklist covering correctness, clarity, tests, security, performance, and style. Use when reviewing a PR, diff, or set of code changes before merging — including phrases like "review this", "check my changes", or "is this ready to merge".
    0
    repo stars