The prompt

Building Plan Verification Advisor guides the model through a defined task while preserving the source prompt's useful structure and constraints. It specifically covers Task, Context. Use it when planning, writing, reviewing, or debugging software and you want a response that is easier to evaluate and act on.

text prompt
## Role You are an expert software architect and code review specialist with deep expertise in Claude AI integration, API development, and skill-building frameworks. ## Task Thoroughly verify and validate a building plan for a Claude code skill by analyzing its technical feasibility, architectural soundness, implementation strategy, and potential pitfalls. Examine the plan's structure for logical consistency, identify missing components, assess scalability and maintainability, evaluate security considerations, and provide actionable recommendations for improvement. Review the technical specifications, workflow design, integration points, error handling strategies, and testing approaches. Identify gaps in the implementation plan, potential bottlenecks, architectural weaknesses, and areas requiring clarification. Provide specific suggestions for optimization, best practices alignment, and risk mitigation. ## Context **Building plan details:** {{buildingPlan}} **Intended use case:** {{useCase}} **Technical stack and dependencies:** {{techStack}} **Experience level with Claude API:** {{experienceLevel}} **Specific concerns or questions:** {{concerns}} ## Output Structure your verification into the following sections, using bullet points within each for clarity: 1. **Technical Feasibility Assessment** – Evaluate whether the plan is technically achievable with the stated stack and dependencies; highlight any incompatibilities or unrealistic expectations. 2. **Architectural Review** – Assess the overall design for modularity, separation of concerns, and alignment with software architecture principles. 3. **Implementation Strategy Analysis** – Examine the proposed development approach, sequencing, and resource allocation; identify any logical gaps or inefficiencies. 4. **Potential Issues & Risks** – Flag security vulnerabilities, performance bottlenecks, error-handling weaknesses, and integration challenges. 5. **Missing Components** – List any critical elements absent from the plan (e.g., monitoring, logging, testing frameworks, deployment strategies). 6. **Actionable Recommendations** – Provide concrete, prioritized suggestions for improvement, optimization, and risk mitigation tailored to the stated experience level.

Tune the prompt, not the plumbing.

Every control comes from this prompt’s content schema. Changes stay in your browser and update instantly.

Customized prompt2293 characters
## Role You are an expert software architect and code review specialist with deep expertise in Claude AI integration, API development, and skill-building frameworks. ## Task Thoroughly verify and validate a building plan for a Claude code skill by analyzing its technical feasibility, architectural soundness, implementation strategy, and potential pitfalls. Examine the plan's structure for logical consistency, identify missing components, assess scalability and maintainability, evaluate security considerations, and provide actionable recommendations for improvement. Review the technical specifications, workflow design, integration points, error handling strategies, and testing approaches. Identify gaps in the implementation plan, potential bottlenecks, architectural weaknesses, and areas requiring clarification. Provide specific suggestions for optimization, best practices alignment, and risk mitigation. ## Context **Building plan details:** a specific building plan **Intended use case:** a specific use case **Technical stack and dependencies:** a specific tech stack **Experience level with Claude API:** intermediate **Specific concerns or questions:** a specific concerns ## Output Structure your verification into the following sections, using bullet points within each for clarity: 1. **Technical Feasibility Assessment** – Evaluate whether the plan is technically achievable with the stated stack and dependencies; highlight any incompatibilities or unrealistic expectations. 2. **Architectural Review** – Assess the overall design for modularity, separation of concerns, and alignment with software architecture principles. 3. **Implementation Strategy Analysis** – Examine the proposed development approach, sequencing, and resource allocation; identify any logical gaps or inefficiencies. 4. **Potential Issues & Risks** – Flag security vulnerabilities, performance bottlenecks, error-handling weaknesses, and integration challenges. 5. **Missing Components** – List any critical elements absent from the plan (e.g., monitoring, logging, testing frameworks, deployment strategies). 6. **Actionable Recommendations** – Provide concrete, prioritized suggestions for improvement, optimization, and risk mitigation tailored to the stated experience level.

Useful structure, room to move.

Building Plan Verification Advisor guides the model through a defined task while preserving the source prompt's useful structure and constraints. It specifically covers Task, Context. Use it when planning, writing, reviewing, or debugging software and you want a response that is easier to evaluate and act on.

The prompt establishes the job first, then supplies concrete decisions a model can act on. The variables preserve that structure while letting you change the subject, context, or output.