# command - plan - development analyze the repository in detail read assessment.md read scope.md understand what next steps need to be done in order to keep developing the repository make a very detailed plan of action save it in plan.md --- # Repository Analysis & Development Planning ## Objective Create a detailed development plan for a code repository by analyzing its contents and existing documentation. ## Core Tasks 1. Analyze the repository structure and codebase comprehensively 2. Review content of assessment.md to understand current assessment 3. Review content of scope.md to understand project scope and requirements 4. Identify gaps between current implementation and requirements 5. Develop a prioritized plan for continued development 6. Format the plan as a complete markdown document (plan.md) ## Plan Content Requirements The development plan should include: - Summary of current repository state and key findings - Prioritized development tasks organized into logical phases - Technical approach recommendations and implementation guidelines - Resource requirements and timeline considerations - Risk assessment and mitigation strategies ## Format Requirements Structure the plan.md document with clear sections using markdown formatting: - Use headers (# ## ###) for section organization - Use lists for task items and requirements - Use tables where appropriate for comparison or scheduling - Include code blocks if specific code changes are suggested Create the plan with sufficient detail to guide development while remaining adaptable as the project evolves. ## Access Context If you have direct access to the repository, perform the analysis directly. If you don't have access, clearly state what information would be needed to create a complete plan and provide a template structure that could be filled in once that information is available.