Plan an alternative to existing software
Start with the work people need to do. A useful alternative solves a specific problem; it does not need to copy every feature of an established product.
Describe the gap
Write down who uses the current tool, which tasks fail, and what a better outcome looks like. Separate essential tasks from preferences. Include constraints such as accessibility, data export, deployment environment, and ongoing maintenance. A concrete example is more useful than a long feature wish list.
Use evidence responsibly
CSR Create accepts a description and supports research and requirements refinement. If you provide existing-software materials for analysis, use only materials you are allowed to share. Keep account details, customer information, credentials, and private source out of public descriptions. Research findings still need your review; they are not proof that a replacement is technically or legally equivalent.
Compare reuse with new work
Look for components that cover individual capabilities. Record license, source, version, and unresolved compatibility questions. A repository link is a starting point for evaluation, not permission to integrate everything it contains. Confirm ownership and license obligations before implementation.
Make the next step small
Use the guided workflow to choose architecture, delivery, release governance, and a coding-tool handoff. Export a Markdown plan or ZIP for your development workspace. Start with one useful end-to-end task and define how you will verify it before expanding scope. CSR planning does not automatically build or deploy the application.