What's new in v2.1.0

This release adds everything needed to publish spec-kit-onboard to the spec-kit community catalog.

Changes

• extension.yml — new manifest in spec-kit community schema v1.0; command names follow the required speckit.onboard.* pattern
• catalog-entry.json — ready-to-submit entry for github/spec-kit's catalog.community.json
• .extensionignore — excludes dev-only files (spec-kit-onboard.md, Makefile, .markdownlint.json) from packaged releases
• LICENSE — renamed from LICENSE.md to comply with community publishing requirements
• extension.json — retained for backwards compatibility with spec-kit v1.x; version bumped to 2.1.0

Submitting to the community catalog

To list this extension in the spec-kit community catalog, open a PR against github/spec-kit adding the contents of catalog-entry.json as a new entry in extensions/catalog.community.json.

• Interactive quiz mode: new after-explain hook suggests /onboard quiz automatically at the right moment (after reading ≥ 3 artifacts, after reading all specs of a feature, or after 7 days since last quiz) — no need to type the command manually
• Question history: quiz_questions_history[] added to the profile (schema v2.0); every question asked is persisted with artifact + topic fingerprint, guaranteeing no question is ever repeated across sessions
• Multi-developer support: /onboard start now creates per-developer profiles at .onboard/profiles/<name>.json; all commands resolve the active profile by name; legacy profile.json is migrated automatically; prompts to select a profile when multiple exist and --dev is not specified
• Profile schema bumped to v2.0: new fields quiz_questions_history, implementation_attempts, last_mentor_suggestion, last_quiz_nudge

• New command /onboard team: aggregated view of all developer profiles in .onboard/; supports single and multi-profile layouts
• /onboard team --report: exports full team progress report to .onboard/team-report.md with per-developer sections, feature coverage, gaps, and recommendations
• /onboard mentor now integrates with jira and azure-devops extensions: appends linked issue/work item status and URL to the task briefing when available

• --format mermaid in /onboard trail: interactive diagram with color coding by task status (green/blue/red), click handlers linking to task files, and subgraphs grouping completed vs open tasks
• docguard integration in /onboard explain: displays quality score and failing criteria before the explanation, integrated into the explanation body per developer level
• New hook before-implement: automatically tracks spec-aware badge by checking whether the developer has read all specs before starting implementation; displays a non-blocking advisory if specs are unread

1.0.0 — 2026-03-26

• Initial release
• 6 commands: start, explain, trail, quiz, badge, mentor
• 1 hook: after-implement
• 9 badges in the catalog
• Passive integration with cleanup, verify, docguard, learn