write-goals

原文涵盖的主题

• Write the goals document
• 1. Find the shared files
• 2. Read before you ask
• 3. Ask, one section at a time
• 4. Write the file
• 5. Check it
• 6. Show it and hand over

The agent-pr-pipeline skill does not start without a goals document. Its product-fit reviewer checks every plan against it. Only the maintainer decides what the product is for, so this skill asks and writes down the answers. It never invents a goal, a non-goal or a user. Summary: read the repo, ask the maintainer section by section, write their answers into the template, check the file with the script, and ask them to approve it. The template and the checker are in the agent-pr-pipeline plugin folder: If either file is missing, stop and tell the user to install the agent-pr-pipeline plugin (see its README). Read the README, AGENTS.md or CLAUDE.md, and any existing goals, vision or roadmap file. Use them only to ask sharper questions, for example: "The README says it runs without a server. Is 'no hosted service' a non-goal?" A sentence in the README is not a goal until the maintainer says so. If a goals document already exists, show it and ask what should change. Do not overwrite it without a yes. Ask in plain words and wait for each answer. Ask a follow-up when an answer is vague. 1. What the product is. "In one or two sentences: what is it, and who is it for?" 2. Goals. "What shou

这里只展示节选，请以完整原文和当前要求为准。