Skip to content

join-the-team v0.1.3 — planning starts at init

Choose a tag to compare

View all tags
@jpantsjoha jpantsjoha released this 21 Jul 10:44
· 31 commits to main since this release
v0.1.3
ddabf8d

Planning becomes part of the installed operating system

join-the-team now gives a human–AI delivery team more than a governance contract on day one. Bootstrap and init seed the minimum durable records needed to turn accepted intent into coordinated delivery: a product vision, shared delivery workflow, roadmap, current status, and project changelog.

The value is practical: Product Owners have an explicit acceptance boundary, planners preserve intent and interfaces, workers receive bounded tasks, and repository records no longer compete silently with the active work tracker. Better planning reduces duplicated discovery, context churn, merge conflict, rework, and avoidable agent spend.

What is new

  • Planning seed at init: project-neutral VISION.md, DELIVERY-WORKFLOW.md, ROADMAP.md, STATUS.md, and CHANGELOG.md templates are installed alongside the operating model.
  • One workflow above the skills: the generated workflow connects Product Owner validation, delivery orchestration, planner/worker separation, integration, independent review, release, observation, and learning.
  • Safe adoption for existing projects: existing planning records are preserved; only missing records are seeded. Conflicting operating contracts or surface adapters still stop before writes begin.
  • Approved dual-record architecture: repository documents own durable intent and decisions; GitHub or another tracker owns active milestones, epics, tasks, assignments, and queue state. Deterministic reconciliation is the design boundary.
  • Clearer init experience: /join-the-team:init, bootstrap guidance, and the day-one example now explain how planning records and human authority are established together.
  • Public privacy policy: the repository now documents local behavior, optional external connections, data handling, and user controls for plugin and marketplace review.

Why this improves delivery value

Agent throughput is only valuable when the plan prevents many workers from multiplying the same ambiguity. This release makes product intent, decisions, ownership, evidence, and re-planning triggers durable before fan-out. The direction is informed by Cursor research on agent-swarm economics, while the plugin makes no claim that external experimental savings automatically reproduce in every project.

Research: https://cursor.com/blog/agent-swarm-model-economics

Upgrade and compatibility

This is a backward-compatible 0.1.x enhancement. Existing adopters can rerun init safely: matching operating files remain unchanged, existing project planning records are reported and preserved, and missing planning files are added. Start with the dry-run documented in BOOTSTRAP.md.

Validation

  • 79 Markdown files linted with zero errors
  • 16 unit tests passed
  • clean-init, dry-run/no-write, preservation, idempotency, conflict-atomicity, drift, binding, and evidence cases covered
  • operating-model template validation passed
  • cross-harness plugin packaging and manifest validation passed

Scope boundary

This release delivers the bootstrap planning-seed slice of approved DPS-001. Cross-skill lifecycle enforcement, issue templates, and deterministic live-tracker reconciliation remain explicit follow-up work rather than being presented as complete.

Full change: #6

Assets 2
Loading