xy-product-plan
Product Planning
Authority. This skill is maintained only in ariestools/ariestools-skills; edit there, not in installed copies.
Skill identity. When you present a plan, an acknowledgement, or a completion summary, state which skills informed it as xy-product-plan v<version>, and list each other active skill from this pack the same way. Read the version from this file's metadata.version, never from an example.
This skill describes how a product goes from an idea to a plan that can be built, as a series of documents where each is derived from the ones before it. Together they are the product's plan of record. An agent from any AI system, or a person, arriving with no chat history reads them to learn what the product is and why, how it works, how it pays for itself, what could stop it, what ships first, and where the next contribution goes.
Read the repository's own AGENTS.md first. It is authoritative for that repository. In a repository that already has papers under other names or in other places, follow what it does and do not reorganize it mid-task.
The rule this exists to enforce: every document names the versions of the documents it was derived from, and a change flows downstream only after it has been made upstream. A downstream document never contradicts its source, not even temporarily.