Cris Weber
Community@crisweber2600
Cris Weber maintains the Lens Workbench skill suite: a governed feature-lifecycle system for planning, developing, and auditing software features across clean-room repositories.
Agent Skills by Cris Weber
Showing 41 vetted skills indexed across 1 GitHub repositories.
crisweber2600lens-work-setup
Registers the LENS Workbench module into BMAD configuration and help systems.
crisweber2600lens-batch
Generates two-pass batch intake files and resumes Lens planning targets after answers are filled.
crisweber2600lens-dev
Orchestrates dev-phase story implementation across epics with git branch and session checkpoint management.
crisweber2600lens-feature-yaml
Read, validate, update, and persist Lens feature.yaml governance state via CLI.
crisweber2600lens-ledger-promotion
Promotes completed feature knowledge into living service, domain, or program ledgers.
crisweber2600lens-reporting-snapshot
Generates read-only stakeholder status snapshots in Markdown and JSON from Lens governance artifacts.
crisweber2600lens-map-audit
Audits LENS/BMAD knowledge maps and ledgers for topology inconsistencies and projection readiness.
crisweber2600lens-complete
Validates and archives completed features in Lens governance repositories with atomic writes.
crisweber2600lens-expressplan
Orchestrates express-track planning by delegating to QuickPlan and enforcing adversarial review gates.
crisweber2600lens-work-intake
Creates durable NextLens feature archives with lifecycle handoff and file-based work memory.
crisweber2600lens-doctor
Diagnoses Lens topology health and routes findings to remediation workflows.
crisweber2600lens-lifecycle
Routes, validates, and advances NextLens feature lifecycle phases using local feature.yaml records.
crisweber2600lens-discover
Reconciles local TargetProjects repository clones with the governance repo-inventory.yaml file.
crisweber2600lens-finalizeplan
Consolidates planning artifacts into a dev-ready execution bundle with PR handoff.
crisweber2600lens-topology-design
Creates service, domain, and program topology decision reports for Lens projects.
crisweber2600lens-split-feature
Validates split boundaries and moves stories between governance features via scripted operations.
crisweber2600lens-next
Routes feature lifecycle phases by invoking next-ops.py and delegating to phase conductor skills.
crisweber2600bmad-lens-postflight
Commits, pushes, and verifies clean git state across Lens session repos.
crisweber2600lens-git-orchestration
Executes git write operations for Lens control-repo branch topology and target-repo dev branch preparation.
crisweber2600lens-nextlens-bugfix
Orchestrates governed NextLens bugfixes from bug recording through branch preparation, delegation, and PR closeout.
crisweber2600lens-upgrade
Plans Lens module upgrades and routes legacy topologies to migration paths.
crisweber2600lens-constitution
Resolves and merges 4-level governance constitution hierarchies to validate feature compliance.
crisweber2600lens-techplan
Orchestrates the TechPlan phase by enforcing governance gates and delegating architecture authoring.
crisweber2600bmad-lens-core-bugfix
Orchestrates Lens core bug fixes through branch creation, implementation delegation, and PR automation.
Frequently Asked Questions About Cris Weber
FAQPage SchemaWhat tasks can I perform with Cris Weber's Lens skills?▼
You can initialize features, domains, and services; run planning phases (PrePlan, BusinessPlan, TechPlan, ExpressPlan); conduct dev sprints in clean-room repos; execute governed bugfixes; audit topology maps; promote feature knowledge to ledgers; and generate read-only stakeholder status snapshots.
Who are the Lens Workbench skills designed for?▼
They target software engineers and technical leads managing multi-repository feature development under governance rules. Users running sprint execution, feature splits, branch preparation, and compliance checks against a 4-level constitution hierarchy benefit most from the suite.
How do I install and start using the Lens module?▼
Run lens-setup to install and configure the Lens module in a project, then lens-work-setup to register the LENS Workbench module with its configuration and help system. Use lens-preflight to validate the workspace before governance operations, and lens-doctor to check topology health.
What are the prerequisites and dependencies for Lens skills?▼
Skills require a governance repository with repo-inventory.yaml, local TargetProjects clones reconciled via lens-discover, and git access for branch and commit operations. The lens-next router depends on next-ops.py, and BMAD delegation requires a registered BMAD skill through lens-bmad-skill.
How does Lens enforce governance and compliance during development?▼
Lens resolves applicable rules through lens-constitution using a 4-level hierarchy with additive inheritance. Gates include publish-before-author enforcement, PRD reference checks, adversarial review with blind-spot challenges, commit and path gates on bugfixes, and postflight clean-state verification across touched repos.