prd v05 technical stack selection

Engineering Community

Skill notes

Consumes

This skill requires prior work from v0.3-v0.5: FEA-* feature entries (from v0.3 Features Value Planning) — Every feature translates to technical capability requirements; derives which capability areas need technology decisions SCR-* screen entries (from v0.4 Screen Flow Definition) — Screen count and component complexity informs frontend technology needs; DES- components reveal design system constraints

Produces

This skill creates/updates: TECH-* entries (technology decisions, decision type + rationale) — Decisions for each capability area with categories (Reuse/Extend/New/Replace), options considered, choice made, and rationale tied to FEA-/RISK- constraints Risk-to-Technology mapping table — Validation showing every RISK- entry has corresponding TECH- response or explicit acceptance Technical feasibility artifact — Confidence assessment on whether technology choices support feature MVP-SCOPE and risk mitigations

Workflow Overview

Discover Existing Assets → Read SOT or interview user for current tech stack Categorize Layers → Reuse / Extend / New / Replace for each capability Evaluate Vendor Fit → Check vendor options for New/Replace layers (if constraints exist) Evaluate Alternatives → Research non-vendor options where gaps exist Check Product Family → Shared infrastructure, component reuse, cross-product UX

Decision Categories

Category · Definition · When to Choose Reuse · Existing asset covers this need as-is · Sibling product or prior work already solves this Extend · Existing asset needs augmentation · Asset exists but needs new capabilities for this product New · No existing asset, greenfield decision · No prior work; need full evaluation Replace · Existing asset doesn't fit, needs new solution · Current tool/service is wrong for this product's requirements

Decision Framework

Factor · Favors Reuse/Extend · Favors Buy (Vendor) · Favors Buy (Non-Vendor) · Favors Build Existing asset · Already deployed and working · Vendor has a product · Non-vendor product fits better · Nothing fits Differentiation · Not relevant · Commodity capability · Commodity capability · Core to value prop Vendor alignment · Already committed · Vendor product fits · Vendor has gap or poor fit · No vendor option

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@mattgierhart · MIT
Token usage
Moderate
Setup complexity
Manual integration
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js · Python
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview prd-v05-technical-stack-selection.preview
# Discovery Output

Create a summary table: | Capability Area | Existing Asset | Status | | --- | --- | --- | | [derived from FEA-/RISK-] | [what exists or "None"] | [Reuse / Extend / New / Replace] | ---

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.