Skip to content

Feature request: Merge Hatching Steps 5 and 6 (both are Skills) #27

@Javierif

Description

@Javierif

Is your feature request related to a problem? Please describe.
The current "Hatching" documentation splits Steps 5 and 6 into two separate stages, but in practice they represent the same thing: both are Skills. This duplication can be confusing for readers and contributors (it’s unclear whether there is an intended conceptual difference), and it increases the risk of inconsistent terminology or duplicated documentation over time.

Describe the solution you'd like
Unify Hatching Step 5 and Step 6 into a single step explicitly describing Skills (execution capabilities).

  • Update the Hatching documentation (and any diagrams) so there is one “Skills” step.
  • Use a clear, explicit name for the unified step (e.g., “Skills (Execution Capabilities)” or the project’s preferred terminology).
  • If there is an intended distinction between Step 5 and Step 6, document that distinction explicitly; otherwise, merge them.

Describe alternatives you've considered

  • Keep Steps 5 and 6 separate but rename/rewrite them to clearly reflect different responsibilities (only if there is a real difference in the architecture).
  • Add a short clarification note under each step explaining how they differ (again, only if needed).

Additional context
The goal is to reduce redundancy and improve the mental model of the Hatching process for onboarding and ongoing maintenance.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions