Packages on processkit

minimal

Mon, 01 Jan 0001 00:00:00 +0000

Intended for: solo developers and small side projects. Extends: — (the base tier)

The lightest footprint package. Just enough structure to track work and debug effectively — no roles, no scopes, no governance artifacts.

Included skills

event-log — foundation: probabilistic append-only event log
actor-profile — basic Actor entities
workitem-management — WorkItem creation and transitions
git-workflow — branch/commit/PR conventions
debugging — systematic debug workflow
testing-strategy — unit vs integration vs E2E guidance
error-handling — cross-language patterns

When to upgrade

You’re joining a team → managed
You need formal decision records, scopes, and process artifacts → managed
You’re building production software → software
You’re doing data/ML work → research
You need the kitchen sink → product

Source

src/packages/minimal.yaml

managed

Mon, 01 Jan 0001 00:00:00 +0000

Intended for: small teams with a shared backlog and process cadences. Extends: minimal

The recommended default. Adds roles, decisions, scopes, and all lightweight process artifacts (standups, retros, session handovers) on top of minimal.

What managed adds on top of minimal

Process primitives and cross-cutting process skills: role-management, decision-record, scope-management, category-management, cross-reference-management, binding-management, process-management, state-machine-management, gate-management, schedule-management, constraint-management, discussion-management, metrics-management.

process-management, schedule-management, and state-machine-management are included for legacy v1 migration guidance. They are not first-class v2 primitive authoring surfaces.

software

Mon, 01 Jan 0001 00:00:00 +0000

Intended for: software engineering teams building production systems. Extends: managed

The “serious software team” tier. Adds architecture, API, database, infrastructure, security, observability, and performance skills on top of managed.

Highlights

Architecture: software-architecture, system-design, domain-driven-design, event-driven-architecture, concurrency-patterns
API: api-design, graphql-patterns, grpc-protobuf, webhook-integration
Database: database-modeling, database-migration, sql-patterns, sql-style-guide, nosql-patterns, caching-strategies
Infrastructure: ci-cd-setup, container-orchestration, dockerfile-review, kubernetes-basics, terraform-basics, linux-administration, dns-networking, shell-scripting
Security: auth-patterns, secret-management, secure-coding, threat-modeling, dependency-audit
Observability: logging-strategy, metrics-monitoring, alerting-oncall, distributed-tracing
Performance: performance-profiling, load-testing

When to upgrade

Only if you also need design, mobile, frontend framework skills → product.

research

Mon, 01 Jan 0001 00:00:00 +0000

Intended for: research teams, data science projects, ML engineering. Extends: managed

Managed plus data, ML, AI, and research-documentation skills.

Highlights

Data: data-science, data-pipeline, data-quality, data-visualization, feature-engineering, pandas-polars, database-modeling, sql-patterns
AI/ML: ai-fundamentals, ml-pipeline, prompt-engineering, llm-evaluation, embedding-vectordb, rag-engineering, code-generation
Research authoring: latex-authoring, documentation, infographics, excalidraw
Infrastructure bits research projects touch: shell-scripting, container-orchestration

Source

src/packages/research.yaml

product

Mon, 01 Jan 0001 00:00:00 +0000

Intended for: end-to-end product development teams. Extends: software

The most comprehensive tier. Software plus design, mobile, framework, and product-specific skills. Use when engineering, design, research, and operations all live in the same repository.

What product adds on top of software

Design: frontend-design, mobile-app-design, logo-design
Framework: fastapi-patterns, tailwind, typescript-patterns, flutter-development, reflex-python
Data subset: data-visualization, feature-engineering, ai-fundamentals, prompt-engineering, llm-evaluation
Language conventions: python-best-practices, rust-conventions, go-conventions, java-patterns
Documentation: latex-authoring, excalidraw, infographics
Product ops: seo-optimization, agent-management

When NOT to use product

If you don’t actually need design, mobile, or framework skills — stick with software. The product tier is large and expecting every team to manage it is false economy.