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-osUpdate marketplace
/plugin marketplace update johns-osUpdate plugin
/plugin update 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 here. Plugin-specific changes remain in each plugin's `CHANGELOG.md`.
## [Unreleased]
### Added
- Root Ruff, yamllint, pre-commit, development dependency, and GitHub Actions CI configuration.
- Cross-surface marketplace tests and a single `scripts/validate-repo.py` quality command.
- Public contribution, security, conduct, support, and issue-template documentation.
- Safe `.env.example` placeholders for optional live council adapters.
### Changed
- Documented the repository architecture and active/unreleased plugin boundary in the root README.
- Fixed existing Ruff lint errors and formatted Python source under the repository lint contract.