From zensu
Bootstrap a new Zensu product from a vision document through to a fully configured product with features, journeys, security profiles, tiers, and a CLAUDE.md.
How this skill is triggered — by the user, by Claude, or both
Slash command
/zensu:bootstrapThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Bootstrap a new Zensu product from a vision document through to a fully configured product with features, journeys, security profiles, tiers, and a CLAUDE.md.
Bootstrap a new Zensu product from a vision document through to a fully configured product with features, journeys, security profiles, tiers, and a CLAUDE.md.
This is the greenfield entry point — a new product captured from a plan/vision doc, before (or independent of) any code.
Brownfield instead? Code already exists and its features are untracked → use /zensu:ghost-scan.
Hybrid (existing code and this plan doc)? Run /zensu:ghost-scan first to import what is built, then create the plan's not-yet-built items as planned features — see that skill's Phase 6.
curl -fsSL https://zensu.dev/install.sh | sh) and on PATHzensu auth login (check with zensu auth status)Every command accepts --json for machine-readable output; run zensu <noun> <verb> --help for the full flag set.
Execute these phases in order. Present results to the user after each phase and wait for confirmation before proceeding.
Workflow gate (first + last action). As the VERY FIRST action, run bash "$(cat "$HOME/.zensu/plugin-root")/hooks/lib/zensu-log.sh" --workflow-begin --tools "create_product,create_product_vision,bootstrap_from_vision,apply_bootstrap,create_feature,add_subfeature,create_tier,set_feature_tiers,create_user_journey,create_journey_step,split_feature,update_feature,update_bootstrap_step,generate_claude_md,generate_threat_model,analyze_feature_security". This marks the Zensu product workflow active so the CLI write-gate (hooks.mcpGate, default-on) recognizes this skill's zensu products create / zensu products vision-create / zensu products bootstrap-apply / zensu features create commands as workflow-driven rather than freelance and does not block them. As the VERY LAST action (after Phase 4, or on early exit), run bash "$(cat "$HOME/.zensu/plugin-root")/hooks/lib/zensu-log.sh" --workflow-end.
zensu products create with name, slug, and product typezensu products vision-create --product <product-id> --content <plan-document> --source claude-codezensu products vision-get <vision-id> to get the vision contentzensu products bootstrap-apply <vision-id> --result '<json>' with the structured JSON containing components and featuresplanned with no revision baseline — there is nothing built yet to capture; a feature gets its v1 revision at implement-time (/zensu:implement), or at discovery if /zensu:ghost-scan later finds it already builtExecute each step below, presenting results to the user after each.
Step 1: Review & Refine Features
zensu features list --product <product-id>)zensu subfeatures add <feature-id> or zensu features split <feature-id>zensu features createzensu features update <feature-id>zensu products bootstrap-step <vision-id> --step 1Step 2: Define User Journeys
zensu journeys suggest --product <product-id> to get product context for journey suggestionszensu journeys create --product <product-id> (include title, slug, journey type, priority, persona)zensu journeys step <journey-id> --product <product-id>:
--step-order--feature--interaction-type (action|navigation|input|validation|output|wait)--criticalzensu journeys health --product <product-id> <journey-id> on each journey to identify weak linkszensu products bootstrap-step <vision-id> --step 2Step 3: Deepen Security Setup
zensu security analyze <feature-id> on all confidential/restricted featureszensu security suggest-tests <feature-id> on high-risk features to identify needed testszensu security threat-model <feature-id> on the most critical feature for STRIDE analysiszensu products bootstrap-step <vision-id> --step 3Step 4: Set Up Tier Availability (Optional)
zensu tiers create --product <product-id> for each tier (ascending tier order: 1, 2, 3...)zensu tiers set-feature <feature-id> for each feature:
zensu tiers matrix --product <product-id> to show the complete matrixzensu products bootstrap-step <vision-id> --step 4 (or --step 5 if skipping)Step 5: Generate CLAUDE.md
zensu doc claude-md --product <product-id> --variant fullzensu products bootstrap-step <vision-id> --step 5Present a final summary:
The product is now ready for implementation. Features can be worked on using the /zensu:implement skill.
| Command | Phase | Purpose |
|---|---|---|
zensu products create | 1 | Create the product |
zensu products vision-create | 1 | Store the vision document |
zensu products vision-get | 2 | Get vision content for analysis |
zensu products bootstrap-apply | 2 | Create components and features from decomposition |
zensu features list | 3.1 | Review bootstrapped features |
zensu features update | 3.1 | Fix priorities, descriptions |
zensu subfeatures add | 3.1 | Split large features |
zensu features split | 3.1 | Split features into children |
zensu features create | 3.1 | Add missing features |
zensu journeys suggest | 3.2 | Get context for journey suggestions |
zensu journeys create | 3.2 | Create journeys |
zensu journeys step | 3.2 | Add steps to journeys |
zensu journeys health | 3.2 | Check journey health |
zensu security analyze | 3.3 | Analyze feature security |
zensu security suggest-tests | 3.3 | Get security test suggestions |
zensu security threat-model | 3.3 | Generate STRIDE threat model |
zensu tiers create | 3.4 | Create pricing tiers |
zensu tiers set-feature | 3.4 | Assign features to tiers |
zensu tiers matrix | 3.4 | Show tier matrix |
zensu doc claude-md | 3.5 | Generate CLAUDE.md template |
zensu products bootstrap-step | 3.x | Track post-bootstrap progress |
Provides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.
npx claudepluginhub mkitconsulting/zensu-claude-code --plugin zensu