← all publishers

projectious-work

@projectious-work source repo

Report this profile Claim this profile

• 465 skills
• 0 followers
• 2 weeks ago last updated

1. ▌
   Fastapi Patterns 2 · projectious-work bundle

   FastAPI patterns — dependency injection, Pydantic models, async endpoints, middleware, and testing. Use when building FastAPI applications, designing API endpoints, adding authentication, or reviewing FastAPI code.
   0 repo stars
2. ▌
   GRAPHQL Patterns 2 · projectious-work

   GraphQL schema design, resolver patterns, DataLoader, pagination, federation, and schema evolution. Use when designing a GraphQL schema, implementing resolvers, diagnosing N+1 problems, adding pagination, setting up federation, or evolving a schema without breaking clients.
   0 repo stars
3. ▌
   Rust Conventions 2 · projectious-work

   Rust conventions — error handling with anyhow/thiserror, module layout, clippy. Use when writing or reviewing Rust code, organizing modules, or deciding on error handling, naming, and testing conventions.
   0 repo stars
4. ▌
   Testing Strategy 2 · projectious-work

   Testing approach — unit vs integration vs E2E, coverage goals, organization. Use when deciding what to test, choosing between unit/integration/E2E tests, planning a test strategy for new functionality, or setting coverage goals.
   0 repo stars
5. ▌
   Context Archiving 2 · 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
6. ▌
   Model Recommender 5 · 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
7. ▌
   Model Recommender 6 · 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
8. ▌
   Binding Management 2 · projectious-work bundle

   Manage Binding entities — scoped, temporal, many-to-many relationships between any two primitives. Use when a relationship between two entities 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 the release process only on the main branch'.
   0 repo stars
9. ▌
   Process Management 2 · projectious-work bundle

   Manage Process entities — declarative sequences of steps with roles, gates, and a definition of done. Use when defining a reusable workflow — code review, release, incident response, onboarding — that the project wants to run consistently.
   0 repo stars
10. ▌
    Database Modeling 2 · projectious-work bundle

    Data modeling — ER diagrams, normalization, denormalization trade-offs, relationship patterns, and schema evolution. Use when designing a new schema, critiquing an existing data model, choosing between normalized and denormalized designs, or modeling complex relationships like polymorphism, hierarchy, or temporal data.
    0 repo stars
11. ▌
    Secret Management 2 · projectious-work

    Handle secrets safely — env vars, .env files, vaults, rotation. Use when dealing with API keys, passwords, tokens, database credentials, or any other sensitive value the application needs at runtime.
    0 repo stars
12. ▌
    Processkit Gateway 2 · 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
13. ▌
    Artifact Management 2 · 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
14. ▌
    Category Management 2 · 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
15. ▌
    Schedule Management 2 · projectious-work bundle

    Manage Schedule entities — time-based triggers and recurring cadences (daily standup, weekly review, monthly retro). Use when defining a recurring cadence — daily/weekly/monthly — that triggers a process or reminder.
    0 repo stars
16. ▌
    Workitem Management 3 · 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
17. ▌
    Container Orchestration 2 · projectious-work bundle

    Docker Compose patterns for multi-service apps — health checks, networking, volumes, dependencies. Use when writing or editing docker-compose files, designing multi-service architectures, debugging container networking, or managing volumes and service dependencies.
    0 repo stars
18. ▌
    Caching Strategies 2 · projectious-work

    Caching patterns — cache-aside, write-through, TTL strategies, invalidation, HTTP caching. Use when adding caching to reduce latency or DB load, choosing between caching patterns, configuring HTTP cache headers, debugging stale data or stampedes, or designing an invalidation strategy.
    0 repo stars
19. ▌
    Database Migration 2 · projectious-work

    Schema migration workflows — zero-downtime expand/contract, batched backfills, and rollback strategies. Use when planning a schema migration, reviewing migration scripts, troubleshooting a slow or failed migration, or rolling back a deployed change.
    0 repo stars
20. ▌
    Workitem Management 4 · 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
21. ▌
    Migration Management 7 · projectious-work bundle

    Manage Migration entities — pending, in-progress, and applied transitions between upstream source versions. Use when an upstream source bumps version (processkit, aibox, 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
22. ▌
    Status Update Writer 2 · 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
23. ▌
    Migration Management 8 · projectious-work bundle

    Manage Migration entities — pending, in-progress, and applied transitions between upstream source versions. Use when an upstream source bumps version (processkit, aibox, 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
24. ▌
    Flutter Development 2 · projectious-work bundle

    Flutter and Dart development — widget architecture, state management, navigation, and cross-platform layout. Use when building Flutter apps, choosing a state-management approach, designing responsive layouts, or reviewing widget code.
    0 repo stars
25. ▌
    Integration Testing 2 · projectious-work bundle

    Integration and E2E testing patterns — testcontainers, fixtures, API mocking, snapshots, and CI isolation. Use when writing integration tests against databases, APIs, or queues; setting up testcontainers or fixture infrastructure; mocking external APIs; or debugging flaky tests.
    0 repo stars
26. ▌
    Typescript Patterns 2 · projectious-work

    TypeScript patterns — strict mode, discriminated unions, runtime validation, Result types. Use when writing or reviewing TypeScript, setting up a project's tsconfig, or designing type-safe data flows.
    0 repo stars
27. ▌
    Webhook Integration 2 · projectious-work

    Webhook design and consumption — payload format, HMAC signatures, idempotency, retries, dead-letter queues, security. Use when implementing a webhook consumer, designing an event-notification system, adding signature verification, or debugging duplicate or failed webhook deliveries.
    0 repo stars
28. ▌
    Migration Management 9 · projectious-work bundle

    Manage Migration entities — pending, in-progress, and applied transitions between upstream source versions. Use when an upstream source bumps version (processkit, aibox, 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
29. ▌
    Migration Management 10 · projectious-work bundle

    Manage Migration entities — pending, in-progress, and applied transitions between upstream source versions. Use when an upstream source bumps version (processkit, aibox, 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
30. ▌
    Constraint Management 2 · 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
31. ▌
    Discussion Management 2 · 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
32. ▌
    Research With Confidence 2 · 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
33. ▌
    Concurrency Patterns 2 · projectious-work bundle

    Concurrency and parallelism patterns — async/await, threads, actors, channels, deadlock prevention. Use when choosing a concurrency model, designing concurrent or parallel pipelines, debugging deadlocks or race conditions, or reasoning about shared state and backpressure.
    0 repo stars
34. ▌
    Domain Driven Design 2 · projectious-work bundle

    Domain-Driven Design strategic and tactical patterns — bounded contexts, aggregates, value objects, context mapping. Use when modeling a complex business domain, defining microservice boundaries, designing aggregates, establishing a ubiquitous language, or refactoring a big ball of mud into well-defined contexts.
    0 repo stars
35. ▌
    Migration Management 11 · projectious-work bundle

    Manage Migration entities — pending, in-progress, and applied transitions between upstream source versions. Use when an upstream source bumps version (processkit, aibox, 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
36. ▌
    Migration Management 12 · 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
37. ▌
    Dependency Management 2 · projectious-work

    Cross-language dependency management — lockfiles, version pinning, automated updates, security, and licenses. Use when setting up or reviewing lockfile strategy, configuring automated dependency updates, auditing dependencies for security or license issues, handling monorepo dependencies, or deciding whether to vendor.
    0 repo stars
38. ▌
    Microservice Creation 2 · projectious-work

    Designs and scaffolds new microservices — covering service boundary identification, inter-service communication patterns, containerisation, and orchestration. Use when asked to create a new service, extract a microservice from a monolith, design a service boundary, choose a communication pattern (REST vs gRPC vs events), or set up container orchestration for a multi-service system.
    0 repo stars
39. ▌
    Performance Profiling 2 · projectious-work bundle

    Performance analysis and profiling for CPU, memory, and I/O — flame graphs, benchmarks, regression detection. Use when identifying performance bottlenecks, profiling CPU/memory/I/O, interpreting flame graphs, setting up benchmarking or regression detection, or optimizing a slow function or endpoint.
    0 repo stars
40. ▌
    Python Best Practices 2 · projectious-work

    Python conventions and patterns — typing, testing, project layout, tooling. Use when writing or reviewing Python code, setting up a new Python project, or deciding on tooling, typing, or testing conventions.
    0 repo stars
41. ▌
    Software Architecture 2 · projectious-work bundle

    Codebase architecture analysis — patterns, ADRs, structural review, C4 diagrams. Use when evaluating a codebase's architecture, choosing a pattern for a new project, writing an Architecture Decision Record, reviewing for layer violations, or generating C4 diagrams.
    0 repo stars
42. ▌
    State Machine Management 2 · projectious-work bundle

    Define and customize StateMachine entities — the state/transition graphs used by WorkItems, DecisionRecords, and other primitives with lifecycle. Use when a project needs to customize the default state machine for a primitive (add states, change transitions) or define a state machine for a custom entity type.
    0 repo stars
43. ▌
    Software Modularization 2 · projectious-work

    Design and evaluate module and package boundaries for maintainability, low coupling, and AI agent context efficiency.
    0 repo stars
44. ▌
    Cross Reference Management 2 · 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
45. ▌
    Event Driven Architecture 2 · projectious-work bundle

    Event-driven systems — pub/sub, event sourcing, CQRS, sagas, broker selection, reliability. Use when designing or migrating to an event-driven system, choosing a message broker, implementing event sourcing or CQRS, designing sagas, or reviewing async architectures for reliability and ordering.
    0 repo stars
46. ▌
    Event Log 2 · 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
47. ▌
    Event Log 3 · 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
48. ▌
    Release Semver 3 · 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
49. ▌
    Event Log 4 · 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
50. ▌
    Pk Doctor 6 · projectious-work bundle

    Aggregator health-check for a processkit-managed repository. Runs a fixed suite of checks over the live context/ tree plus src/context/ drift, then resolves ERROR / WARN / actionable INFO findings by default. Use when the user invokes `/pk-doctor`, asks "is this repo healthy", or has just finished an upgrade and wants a sanity pass. Info-only mode is opt-in: stop after the report only when the user explicitly says info-only, dry-run, report-only, check-only, or no fixes.
    0 repo stars
51. ▌
    Task Router 2 · 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
52. ▌
    Skill Finder 2 · 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
53. ▌
    Skill Finder 3 · 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
54. ▌
    Actor Profile 2 · 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
55. ▌
    Skill Builder 2 · 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
56. ▌
    Id Management 2 · 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
57. ▌
    Skill Builder 3 · 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
58. ▌
    Skill Finder 4 · 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
59. ▌
    Skill Finder 5 · 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
60. ▌
    Id Management 3 · 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
61. ▌
    Skill Reviewer 2 · 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
62. ▌
    Standup Context 2 · 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
63. ▌
    Decision Record 2 · 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
64. ▌
    Note Management 2 · 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
65. ▌
    Standup Context 3 · 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
66. ▌
    Status Briefing 2 · projectious-work bundle

    Generates a concise status briefing from project context — synthesizing current state, open decisions, key risks, and today's priority actions into a focused session-start orientation. Use at the start of a session when asked for a briefing, "what's the state of things", "catch me up", or "what should I focus on today."
    0 repo stars
67. ▌
    Status Briefing 3 · projectious-work bundle

    Generates a concise status briefing from project context — synthesizing current state, open decisions, key risks, and today's priority actions into a focused session-start orientation. Use at the start of a session when asked for a briefing, "what's the state of things", "catch me up", or "what should I focus on today."
    0 repo stars
68. ▌
    Decision Record 3 · 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
69. ▌
    Standup Context 4 · 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
70. ▌
    Session Handover 2 · 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
71. ▌
    Context Grooming 2 · projectious-work bundle

    Review and prune the project context — archive completed work, summarize stale entries, and propose disabling unused skills.
    0 repo stars
72. ▌
    Index Management 2 · 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
73. ▌
    Session Handover 3 · 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
74. ▌
    Status Briefing 4 · projectious-work bundle

    Generates a concise status briefing from project context — synthesizing current state, open decisions, key risks, and today's priority actions into a focused session-start orientation. Use at the start of a session when asked for a briefing, "what's the state of things", "catch me up", or "what should I focus on today."
    0 repo stars
75. ▌
    Status Briefing 5 · projectious-work bundle

    Generates a concise status briefing from project context after resolving active migrations by default — synthesizing current state, open decisions, key risks, and today's priority actions into a focused session-start orientation. Use at the start of a session when asked for a briefing, "what's the state of things", "catch me up", "pk-resume", or "what should I focus on today." Info-only mode is opt-in.
    0 repo stars
76. ▌
    Model Recommender 2 · 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
77. ▌
    Model Recommender 3 · 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
78. ▌
    Workitem Management 2 · 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
79. ▌
    Migration Management 2 · projectious-work bundle

    Manage Migration entities — pending, in-progress, and applied transitions between upstream source versions. Use when an upstream source bumps version (processkit, aibox, 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
80. ▌
    Migration Management 3 · projectious-work bundle

    Manage Migration entities — pending, in-progress, and applied transitions between upstream source versions. Use when an upstream source bumps version (processkit, aibox, 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
81. ▌
    Migration Management 4 · projectious-work bundle

    Manage Migration entities — pending, in-progress, and applied transitions between upstream source versions. Use when an upstream source bumps version (processkit, aibox, 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
82. ▌
    Migration Management 5 · projectious-work bundle

    Manage Migration entities — pending, in-progress, and applied transitions between upstream source versions. Use when an upstream source bumps version (processkit, aibox, 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
83. ▌
    Migration Management 6 · 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
84. ▌
    Pk Doctor 2 · projectious-work bundle

    Aggregator health-check for a processkit-managed repository. Runs a fixed suite of detect-only checks over the live context/ tree plus src/context/ drift and surfaces ERROR / WARN / INFO findings in a single report. Use when the user invokes `/pk-doctor`, asks "is this repo healthy", or has just finished an upgrade and wants a sanity pass. Detect-only by default; `--fix` / `--fix-all` opt in to scoped repairs that route through existing MCP write tools only — doctor never hand-edits files under `context/`.
    0 repo stars
85. ▌
    Pk Doctor 3 · projectious-work bundle

    Aggregator health-check for a processkit-managed repository. Runs a fixed suite of detect-only checks over the live context/ tree plus src/context/ drift and surfaces ERROR / WARN / INFO findings in a single report. Use when the user invokes `/pk-doctor`, asks "is this repo healthy", or has just finished an upgrade and wants a sanity pass. Detect-only by default; `--fix` / `--fix-all` opt in to scoped repairs that route through existing MCP write tools only — doctor never hand-edits files under `context/`.
    0 repo stars
86. ▌
    Pk Doctor 4 · projectious-work bundle

    Aggregator health-check for a processkit-managed repository. Runs a fixed suite of detect-only checks over the live context/ tree plus src/context/ drift and surfaces ERROR / WARN / INFO findings in a single report. Use when the user invokes `/pk-doctor`, asks "is this repo healthy", or has just finished an upgrade and wants a sanity pass. Detect-only by default; `--fix` / `--fix-all` opt in to scoped repairs that route through existing MCP write tools only — doctor never hand-edits files under `context/`.
    0 repo stars
87. ▌
    Pk Doctor 5 · projectious-work bundle

    Aggregator health-check for a processkit-managed repository. Runs a fixed suite of detect-only checks over the live context/ tree plus src/context/ drift and surfaces ERROR / WARN / INFO findings in a single report. Use when the user invokes `/pk-doctor`, asks "is this repo healthy", or has just finished an upgrade and wants a sanity pass. Detect-only by default; `--fix` / `--fix-all` opt in to scoped repairs that route through existing MCP write tools only — doctor never hand-edits files under `context/`.
    0 repo stars
88. ▌
    Skill Gate 2 · 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
89. ▌
    Skill Gate 3 · 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
90. ▌
    Release Semver 2 · 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
91. ▌
    Team Manager 2 · 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
92. ▌
    Team Manager 3 · 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
93. ▌
    Team Manager 4 · 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
94. ▌
    Team Creator 2 · 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 those tiers. 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
95. ▌
    Retrospective 2 · 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
96. ▌
    Aggregate MCP 2 · 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
97. ▌
    Team Manager 5 · 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
98. ▌
    Runtime Prune 2 · 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
99. ▌
    Sprint Retrospective · projectious-work

    Facilitates team or project retrospectives — what worked, what didn't, action items. Use at the end of a sprint, milestone, or project phase to reflect on what went well, what didn't, and what to try next.
    0 repo stars
100. ▌
     Database Modeling · projectious-work bundle

     Data modeling — ER diagrams, normalization, denormalization trade-offs, relationship patterns, and schema evolution. Use when designing a new schema, critiquing an existing data model, choosing between normalized and denormalized designs, or modeling complex relationships like polymorphism, hierarchy, or temporal data.
     0 repo stars