Skip to content

Rename general.json and don't use it as a default #85

@mindsocket

Description

@mindsocket

general.json is a "somewhat general" schema for a product management-y strategy and oppportunity context tree. Given the breadth of this project, general.json is a significant misnomer. Rename to strategy_general.json.

Also, it no longer makes sense as a fallback default. schema resolution should fail if one isn't specified.

Aside: noting and embracing an emerging but so far implied schema naming convention of {scope}_{flavor}.json (flavor optional) , following existing ost_strict (scope and flavor), and knowledge_wiki (just scope).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions