project-type-determination

Project type determination checks your prompt and plan documents for explicit classifications—POC, MVP, Private, Enterprise, or Open Source—then asks you if the type remains unclear. This configures analysis thresholds downstream for tailored depth.

The workflow classifies projects as POC, MVP, Private, Enterprise, or Open Source. It scans prompting context and plan documents for explicit statements, then prompts you with these options if type cannot be inferred automatically.

The workflow first checks the triggering prompt for explicit type, then scans target documents via Read, Grep, or Glob for explicit statements, and finally asks the user via a question form if type remains unresolved.

The skill outputs a YAML record containing project_type and source attribution, enabling downstream skills like python-plan-optimization to configure analysis thresholds based on the classified project context.

Yes, the skill attempts automatic inference by checking prompts and scanning plan documents for explicit type mentions. User input via question prompt is required only when explicit statements are not found.