lens-techplan

Orchestrates the TechPlan phase by enforcing governance gates and delegating architecture authoring.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/crisweber2600/Lens.Core.Src --skill lens-techplan-crisweber2600
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lens-techplan
Source: https://github.com/crisweber2600/Lens.Core.Src/tree/main/_bmad/lens-work/skills/lens-techplan
Command: npx skills add https://github.com/crisweber2600/Lens.Core.Src --skill lens-techplan-crisweber2600

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams working in a governed multi-phase feature workflow need a reliable way to transition from business planning to technical architecture without skipping required gates like PRD verification, artifact publishing, and constitution enforcement. ## Core Features & Use Cases - Governance Gate Enforcement: Verifies BusinessPlan completion, locates the authoritative PRD, publishes reviewed artifacts to governance, and enforces domain constitution hard gates before any architecture work begins. - Delegated Architecture Authoring: Routes all architecture document creation through the registered Lens BMAD wrapper (bmad-create-architecture) rather than generating content inline. - Adversarial Review & Phase Promotion: Runs phase-completion adversarial reviews, commits artifacts to the correct control branch, and updates feature.yaml to techplan-complete. - Use Case: After finishing a feature's business plan, run this phase conductor to automatically verify prerequisites, generate the architecture document via BMAD, commit it, and advance the feature to the next milestone. ## Quick Start Run the TechPlan phase for my current feature, or specify one directly with --feature-id to generate and commit its architecture document.

Frequently Asked Questions about lens-techplan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run the TechPlan phase for a feature?

Activate the skill with an optional --feature-id argument to target a specific feature. It resolves feature context from .lens/personal/context.yaml, validates governance state, then delegates architecture authoring to the BMAD wrapper.

What happens if the PRD is missing before architecture authoring?

The skill stops immediately with a hard gate error reporting the expected staged docs path. Architecture authoring cannot begin without a locatable PRD; you must run the businessplan phase first or fix the staged docs path.

Does this skill write architecture documents itself?

No, it is a conductor-only skill. All architecture authoring is delegated to the registered Lens BMAD wrapper via bmad-create-architecture, and governance writes go through the publish hook or lens-feature-yaml.

Why does TechPlan fail with a constitution resolution error?

Constitution resolution fails when a required org level is missing or the constitution has a parse error. Run /new-domain or /new-service to scaffold the missing governance levels before retrying the phase.

What prerequisites must complete before TechPlan can start?

The feature's phase must be businessplan-complete or later, businessplan artifacts must be published to governance, the PRD must exist in staged docs, and the businessplan adversarial review must show status responses-recorded.