platform-detection

To detect a project's tech stack and cache results, run a platform detection step at workflow start to generate a platform-context.json file. This caches the primary platform, detected platforms, and monorepo status for downstream workflow reuse.

Platform-context.json stores cached tech stack detection results, including primary_platform, platforms[], and is_monorepo. It guides downstream workflow steps by providing immediate platform context without re-evaluating project root signals.

Yes, tech stack detection supports iOS, Node.js, Rust, Python, and Go projects. It scans project root signals for these specific tech stacks and accurately identifies them in both monorepos and single-repo setups.

Yes, you can manually override the detected tech stack by creating a .feature-marker.json file. This forces a specific platform selection, bypassing automated root signal detection when a manual override is needed.

Caching tech stack detection in platform-context.json prevents redundant platform scans. It performs one-time detection at workflow start, reducing overhead and ensuring consistent platform context for all subsequent steps.

Automated tech stack detection relies on project root signals for monorepos. If root signals are ambiguous or missing, detection may fail unless you manually configure a .feature-marker.json file to force the correct platform.