parallel-explore-feature

To find parallel features without resource clashes, you need to analyze architecture data alongside active resource claims. This skill reads OpenSpec project metadata and coordinator locks to identify high-value features that can be developed simultaneously without overlapping.

Parallel feature feasibility analysis evaluates whether multiple features can be developed simultaneously by checking active resource claims and architecture data. It classifies candidates as FULL, PARTIAL, or SEQUENTIAL to recommend appropriate parallel development workflows.

Checking active resource locks before parallel feature development requires applying a coordinator detection script to the repository. The script maps in-flight feature claims and evaluates overlap using OpenSpec architecture summaries to prevent concurrent development conflicts.

Yes, you need OpenSpec project metadata and architecture summary files to analyze parallel implementation candidates. The automated architecture scan reads these files to surface candidate features and requires an available coordinator for discovery and lock capabilities.

The best way to classify features for parallel or sequential development is by cross-referencing architecture summaries with active resource claims. This analysis rates each candidate as FULL, PARTIAL, or SEQUENTIAL parallel feasibility and recommends the appropriate workflow.

Parallel feature analysis requires a coordinator with discovery and lock capabilities to accurately map active resource claims and prevent conflicts. Without the coordinator providing lock data, the analysis cannot evaluate in-flight feature overlap to determine true parallel feasibility.