vidhi-planlisted

# Plan a Yojana Task ## Entry Requires a yojana task ID (e.g., `project/N`). ## Workflow ### 1. Pull context ``` yojana_context task="<task-id>" shape="working" ``` Read the acceptance criteria, decisions, description, and neighbor context. If acceptance criteria are missing or vague, stop and set the task to `needs-info` with a comment explaining what's unclear. ### 2. Explore the codebase Before planning anything, go find the code. Read the files that this task will touch. Understand the interfaces, the types, the patterns already in use. What to look for: - Files that implement the feature area (or adjacent features) - Test files and testing patterns used in this project - Types, interfaces, or schemas this task will interact with - Configuration or wiring that will need to change Don't skim — read enough to write code against these interfaces. A plan built on guesses about the codebase is worse than no plan. ### 3. Check neighbors Review the 1-hop neighbors from the context bundle. Look for: - **Upstream tasks** (dependencies): are they done? If not, what assumptions are you making about their output? - **Sibling tasks** that touch the same files: will your plan conflict? Call out shared files explicitly. - **Downstream tasks** that depend on this one: does your plan produce what they need? If you find a conflict or dependency issue, comment on the task and flag it to the user before continuing. ### 4. Write the plan Structure: ```markdown ## Approach 1-3