932927b9df
Move completed plan docs to docs/plans/archive/. Add survey migration 046 and reference HTML/plan files. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
102 lines
4.3 KiB
Markdown
102 lines
4.3 KiB
Markdown
# Deferred Procedural Flow Features
|
|
|
|
> **Created:** February 14, 2026
|
|
> **Status:** Backlog — prioritize based on engineer feedback
|
|
> **Related:** Procedural Flows v1 shipped (Phases 1-4 complete, archived)
|
|
|
|
---
|
|
|
|
## Tier 1 — High Impact / Most Requested
|
|
|
|
### Conditional Steps
|
|
Show or hide steps based on intake form values. For example, skip "Configure DNS Forwarders" if the intake form says the DC won't be the primary DNS server.
|
|
|
|
- Requires: step-level `condition` field (e.g., `{ field: "is_primary_dns", operator: "equals", value: "yes" }`)
|
|
- UI: condition builder in StepEditor, runtime evaluation in ProceduralNavigationPage
|
|
- Complexity: Medium
|
|
|
|
### Sub-Checklists Within Steps
|
|
Break a single step into smaller checkable items. For instance, "Install Windows Features" could have sub-items: AD DS, DNS, DHCP.
|
|
|
|
- Requires: `sub_items: { label: string, required: boolean }[]` on ProceduralStep
|
|
- UI: checkable list within StepDetail, all sub-items must be checked before "Mark Complete"
|
|
- Complexity: Low-Medium
|
|
|
|
### Step Templates / Reusable Step Library
|
|
Save commonly used steps (e.g., "Verify DNS resolution", "Create AD OU structure") and insert them into any procedural flow.
|
|
|
|
- Requires: new StepTemplate model, API endpoints for CRUD, "Insert from Library" button in editor
|
|
- UI: step template browser modal, search/filter by category
|
|
- Complexity: Medium
|
|
|
|
---
|
|
|
|
## Tier 2 — Valuable Enhancements
|
|
|
|
### Screenshot Verification Type
|
|
Upload a screenshot as proof of completion for a step. Useful for "confirm the dashboard shows X" type verification.
|
|
|
|
- Requires: file upload endpoint, `verification_type: 'screenshot'` option, image preview in StepDetail
|
|
- Dependency: file attachment infrastructure (Phase 3 roadmap)
|
|
- Complexity: Medium-High
|
|
|
|
### Session Assignment / Handoff
|
|
Assign a procedural session to another engineer, or hand off mid-procedure. Track who completed which steps.
|
|
|
|
- Requires: `assigned_to` field on Session, assignment API, notification on assignment
|
|
- UI: assign button in session list, "Assigned to you" filter
|
|
- Complexity: Medium
|
|
|
|
### Approval Workflows
|
|
Certain steps or entire procedures require manager/lead approval before proceeding. Step marked as "pending approval" until approved.
|
|
|
|
- Requires: approval model, notification system integration, approval status on steps
|
|
- UI: approval request button, approval queue for managers
|
|
- Complexity: High
|
|
|
|
---
|
|
|
|
## Tier 3 — Advanced / Future
|
|
|
|
### AI-Assisted Template Generation
|
|
Describe a procedure in plain text and generate a structured flow with steps, commands, and intake form fields.
|
|
|
|
- Requires: LLM integration, prompt engineering for step generation, review/edit UI
|
|
- Complexity: High
|
|
|
|
### Automated PowerShell/CLI Execution
|
|
Run commands directly from a step against a connected endpoint (via agent or SSH).
|
|
|
|
- Requires: secure agent infrastructure, command execution sandbox, output capture
|
|
- Security: significant — needs careful scoping
|
|
- Complexity: Very High
|
|
|
|
### Branching Hybrid
|
|
Mini decision-tree within a procedure step. "If the server responds with error X, do A. If it responds normally, continue."
|
|
|
|
- Requires: nested decision node within a procedural step, conditional next-step logic
|
|
- Complexity: High
|
|
|
|
### Procedural Code-Mode Editor
|
|
YAML/JSON editor for power users who want to define procedures as code rather than using the visual editor.
|
|
|
|
- Requires: code editor component, schema validation, bidirectional sync with visual editor
|
|
- Complexity: Medium
|
|
|
|
### Template Marketplace
|
|
Share and discover procedure templates across accounts. Community-contributed flows.
|
|
|
|
- Requires: public/private visibility, template publishing flow, discovery/search, ratings
|
|
- Dependency: subscription tier integration (which tiers can publish/access)
|
|
- Complexity: Very High
|
|
|
|
---
|
|
|
|
## Prioritization Notes
|
|
|
|
Start with **Conditional Steps** and **Sub-Checklists** — these are the most common requests from engineers using procedural flows in the field. They're also relatively contained changes that don't require new infrastructure.
|
|
|
|
**Step Templates** would be the next logical addition once multiple procedural flows exist and engineers start noticing repeated patterns.
|
|
|
|
Everything in Tier 3 requires either new infrastructure (file uploads, agent system, LLM integration) or significant architectural work. Defer until Tiers 1-2 are validated.
|