Engineering Lifecycle provides structured workflows for software discovery, requirements, UX, architecture, implementation, testing, release, maintenance, and repository hygiene. It is designed to produce deterministic local artefacts and support disciplined AI-assisted software delivery.
Marketplace metadata
- Marketplace: johns-os
- Version: 0.6.1
- Category: developer-tools
- Licence: MIT
Install
Add marketplace: /plugin marketplace add johnoconnor0/johns-os Install plugin: /plugin install engineering-lifecycle@johns-os
Add marketplace
/plugin marketplace add johnoconnor0/johns-osInstall plugin
/plugin install engineering-lifecycle@johns-osIncluded skills
profile-product-systemUse at the start of product or repo work to understand the product, users, stack, integrations, constraints, and development maturity.map-product-lifecycleUse to identify where a product or initiative sits in the engineering lifecycle and which artifacts are missing.create-discovery-briefUse to turn a product idea, problem, or vague initiative into a clear discovery brief with users, goals, risks, assumptions, and MVP boundary.create-prdUse to produce a practical product requirements document with functional requirements, non-functional requirements, user stories, and acceptance criteria.create-ux-flowUse to map user journeys, screens, states, interactions, edge cases, and handoff requirements for a product or feature.create-design-systemUse to plan or audit UI foundations, design tokens, component inventory, accessibility rules, and implementation mapping.build-ui-prototypeUse to build a lightweight UI prototype, clickable MVP, app shell, dashboard mock, or frontend proof of concept.create-system-mapUse to map actors, components, workflows, data flow, boundaries, risks, and deployment shape for a product system.create-architecture-planUse to turn product and system understanding into architecture decisions, boundaries, trade-offs, and ADR candidates.create-data-modelUse to define entities, relationships, ownership, sensitivity, retention, integrity rules, and migration risks.create-api-contractUse to define service, frontend, backend, webhook, event, or external-system interfaces and their behavioural contracts.create-implementation-planUse to sequence approved work into safe implementation slices with dependencies, tests, verification, rollout, and rollback notes.implement-feature-safelyUse after planning to implement a feature with scoped changes, verification, testing, rollback awareness, and repository hygiene checks.review-changeUse to review a branch, diff, pull request, or local change for correctness, risk, security, maintainability, testing, and release readiness.create-test-strategyUse to define unit, integration, contract, end-to-end, regression, load, security, and manual QA coverage.create-release-planUse to define release preparation, migrations, rollout, monitoring, rollback, support, and post-release verification.run-engineering-councilUse to run an optional structured council review for high-stakes engineering decisions and contested trade-offs.update-repo-hygieneUse to inspect and intentionally update supporting repository hygiene files, conventions, environment examples, and project guidance.build-project-dashboardUse to summarise engineering lifecycle state, action items, risks, decisions, and recent project artifacts in a project dashboard.
Changelog
# Changelog
All notable repository-level changes are documented in this file.
This changelog covers the `johns-os` marketplace, shared repository tooling, public documentation, and changes affecting multiple plugins. Detailed changes to an individual plugin remain in that plugin's own `CHANGELOG.md`.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and versions follow Semantic Versioning where a repository marketplace version was recorded.
## [Unreleased]
No unreleased repository-level changes are currently documented.
## [0.3.0] - 2026-07-16
### Added
- Added the `ai-utilities` plugin, consolidating Claude Code extension authoring, skill review, plan-completion auditing, and audit-resolution workflows.
- Added root Ruff, yamllint, pre-commit, development dependency, and GitHub Actions CI configuration.
- Added `scripts/validate-repo.py` as the single deterministic repository validation entry point.
- Added cross-surface marketplace consistency tests covering Claude Code, Codex, and the local catalogue.
- Added public contribution, security, code-of-conduct, support, issue-template, pull-request-template, funding, and Dependabot configuration.
- Added a safe root `.env.example` for optional engineering-council adapters and test fixtures.
- Added repository-wide editor, line-ending, ignore, and credential-safety defaults.
### Changed
- Repositioned `johns-os` as a public-ready Claude Code and Codex plugin marketplace for software delivery, business development, and AI-assisted repository work.
- Expanded the active marketplace to three plugins: `engineering-lifecycle`, `business-development`, and `ai-utilities`.
- Added Web Lifter homepage metadata to active Claude Code marketplace entries.
- Documented the repository architecture, installation paths, development setup, validation commands, and the boundary between active plugins and `_unreleased/` candidates.
- Standardised Python formatting and linting across the repository.
- Excluded generated `.project/` state and `_unreleased/` working material from the public source boundary and automated checks.
### Fixed
- Resolved existing Ruff findings and formatting drift before public release.
- Corrected historical plugin changelog entries using commit and release history rather than leaving shipped work under `Unreleased`.
## [0.2.0] - 2026-07-10
### Added
- Added the `business-development` plugin with an interview-first `service-outline` workflow.
- Added a service-document analysis agent and quick-mode support to the business-development workflow.
- Added deterministic Linear task synchronisation, human-task ingestion, proactive council orchestration, configurable enforcement, and environment-variable inventory capabilities to `engineering-lifecycle`.
- Added marketplace tooling to update every version surface atomically through the `bump-version` command.
### Changed
- Expanded `johns-os` from a single-plugin marketplace into a multi-plugin catalogue.
- Released marketplace version `0.2.0`, `engineering-lifecycle` version `0.4.0`, and `business-development` version `0.2.0` together.
- Updated Claude Code, Codex, and local catalogue metadata to represent the expanded plugin set.
### Fixed
- Resolved marketplace version drift between plugin manifests, catalogue records, and the Claude Code marketplace entry.
- Fixed environment-example discovery in nested applications and packages.
- Fixed engineering-council triggering and human-task aggregation reliability.
## [0.1.0] - 2026-06-29
### Added
- Established `johns-os` as a plugin marketplace with Claude Code, Codex, and local catalogue metadata.
- Added the official root `.claude-plugin/marketplace.json` manifest so the repository could be installed through Claude Code's marketplace flow.
- Registered the initial `engineering-lifecycle` plugin for structured discovery, requirements, UX, architecture, implementation, testing, release, and repository-hygiene work.
- Added deterministic marketplace discovery and validation commands.
- Added the initial repository README with installation instructions and marketplace architecture.
### Changed
- Promoted the repository from a local catalogue structure to an installable Claude Code marketplace while retaining parallel Codex metadata.
[Unreleased]: https://github.com/johnoconnor0/johns-os/compare/v0.3.0...HEAD
[0.3.0]: https://github.com/johnoconnor0/johns-os/compare/v0.2.0...v0.3.0
[0.2.0]: https://github.com/johnoconnor0/johns-os/compare/v0.1.0...v0.2.0
[0.1.0]: https://github.com/johnoconnor0/johns-os/releases/tag/v0.1.0