Kytip

Kytip is a standalone, provider-agnostic transcript-to-project-memory bundle. It packages the PMing workflow as a terminal-first, file-based workspace tool.

It ships:

• provider-neutral PM roles, instruction packs, and optional agent adapters
• portable skills for meeting packetization and cross-meeting synthesis
• pm-state/ bootstrap artifacts for workspace-level project memory
• a terminal hub for inspecting PMing output as one cohesive surface
• templates and lightweight scripts for bootstrapping and validation

The runtime contract is pm-state/. Kytip does not require ACE, Codex, Claude, or any provider-specific state to function. Optional adapter assets may exist beside the core bundle, but the runtime and TUI operate only on pm-state/.

Runtime characteristics:

• Node-based terminal UI
• TypeScript source plus prebuilt JavaScript runtime
• no third-party runtime dependencies
• suitable for npm / npx distribution

Package Layout

• assets/.agents/PMing/
  • optional adapter-packaged PMing role registry, kernel, and instruction homes
• assets/.agents/skills/
  • portable PMing skill packages
• assets/instructions/
  • workspace-level instruction aliases
• assets/runtime/
  • provider-agnostic runtime tools, including the Kytip TUI
• assets/pm-state/
  • bootstrap project-memory state tree
• assets/templates/
  • ingest, meeting packet, project page, and portfolio brief templates
• assets/references/
  • PMing entity and workflow references
• assets/tasks/
  • operator-facing pipeline/task notes
• assets/scripts/
  • workspace bootstrap and bundle validation helpers

What Ships

The package surface is intentionally narrow:

• published package contents come from package.json#files
• runtime contract is pm-state/
• the shipped CLI/TUI is assets/runtime/kytip_ui.js
• workspace bootstrap stays file-based and does not require agent runtimes

Not part of the package build:

• agent-state/pming/*.md
• repo-local implementation reports or discovery/spec history
• transcript-derived run outputs

Quick Start

1. Bootstrap a target workspace:

pming/assets/scripts/bootstrap-workspace.sh /path/to/workspace

2. Put weekly raw transcript dumps into:

pm-state/ingest/

3. Use any PMing-compatible provider or workflow to generate:

• pm-state/meetings/*.md
• pm-state/ledgers/*.md
• pm-state/projects/*.md
• pm-state/STREAMS.md
• pm-state/PORTFOLIO_BRIEF.md

4. Launch the workspace hub from the terminal:

./kytip

5. Use the PMing bundle in this order:

• meeting-packetizer
• pm-ledger-updater
• stream-reconciler
• portfolio-brief-writer

Kytip Hub

The workspace bootstrap now includes a terminal UI:

• kytip
  • reads only pm-state/
  • shows an overview, kanban, and note browser together
  • lets you move from blockers, gates, actions, and next steps into the underlying notes
  • refreshes from disk while you work

Controls:

• 1 2 3 switch tabs
• h l move across kanban lanes
• j k or arrows move selection
• Enter opens the selected source note
• PageUp / PageDown scroll note content
• r refresh
• q quit

Build And Pack

The npm-facing package includes:

• package.json
• tsconfig.json
• src/kytip_ui.ts
• assets/runtime/kytip_ui.js

Local packaging workflow:

npm run check
npm run pack:dry-run

If you install dev dependencies, you can also rebuild the committed runtime:

npm run build

If you later publish the package under the current name, the ergonomic CLI path is:

npx --package kytip-pm kytip --workspace .

If you want the explicit UI alias, use:

npx --package kytip-pm kytip-ui --workspace .

Internal Design History

The discovery/spec documents in agent-state/pming/ are internal authoring artifacts. They are useful for evolving the PMing workflow, but they are not Kytip runtime artifacts and they are not part of the npm build surface.