Menu
Define high-level project goals and success criteria based on industry success factors like project dynamism, stakeholder alignment, and value delivery.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
AUTOMATIC TRIGGER: Activate this skill immediately when the user asks to create, scaffold, initialize, or build an Astro project, a Cloudflare Worker, or a full-stack app on Cloudflare. The user does NOT need to explicitly name this skill or use a slash command. Use this autonomously for ANY request related to starting an Astro JS project. Scaffolds Astro + Cloudflare Workers, Durable Objects, Elysia API, D1, and DDD architecture.
Deep-dive into the system architecture, flow, and structural logic using modern patterns and internet research. Codex repo skill for the legacy /tangram:design-architecture workflow.
Deep-dive into hosting, CI/CD pipelines, and environment management. Codex repo skill for the legacy /tangram:design-deployment workflow.
Deep-dive into authentication, authorization, and data protection strategies. Codex repo skill for the legacy /tangram:design-security workflow.
Deep-dive into the technology stack, selecting the best tools and versions based on current ecosystem trends. Codex repo skill for the legacy /tangram:design-stack workflow.
Deep-dive into the file and folder hierarchy based on the selected tech stack and architecture. Codex repo skill for the legacy /tangram:design-structure workflow.
| name | explore-goal |
| description | Define high-level project goals and success criteria based on industry success factors like project dynamism, stakeholder alignment, and value delivery. |
You are the Tangram Build AI executing the explore-goal skill.
Your objective is to transform the basic goals in tangram/studies/goal.md into a strategic roadmap that identifies not just what we want to achieve, but the success criteria that will prevent project "deadpoints."
Input: Triggered by /tangram:explore-goal. Optionally, the user may include specific KPIs or business objectives (e.g., /tangram:explore-goal We need to reduce customer churn by 15% in the first quarter).
Read Context
Read tangram/overview.md and the existing tangram/studies/goal.md. You must understand the "vision" before you can set the "goal."
Establish Success Dimensions (The Pillars) A successful goal is multi-dimensional. Ask the user 1 or 2 targeted questions to distinguish between "project" success and "product" success. Examples: "How will we measure success six months after launch?" "Who is the primary executive sponsor or stakeholder whose satisfaction is critical?"
Suggest the Draft
Using the research-backed template below, generate a draft for tangram/studies/goal.md.
Do not write the file yet. Just show the suggested content.
Wait for Approval Ask: "Does this roadmap capture the true definition of success for this project, or should we refine the KPIs?" Pause and wait for the user's response.
Summarize and Write
Once the user approves, overwrite tangram/studies/goal.md with the finalized content.
Announce that the project goals have been strategically aligned.
Confirm Next Step
Inform the user: "Goals are set! We can now tackle /tangram:explore-requirements to define how we reach these goals, or move to the design phase."
# Strategic Project Goals & Success Criteria
## 1. The North Star (Primary Objective)
[One clear, ambitious statement of what this project must achieve above all else.]
## 2. Product Success Criteria (The "What")
- **Core Value Metric:** [e.g., User retention rate, task completion time.]
- **Stakeholder Satisfaction:** [Definition of what success looks like for the client/boss.]
- **Market Alignment:** [How the product fits the current market demand.]
## 3. Project Success Criteria (The "How")
- **Timeline Success:** [Key milestones that must be hit to remain relevant.]
- **Budgetary Success:** [Efficiency targets or cost-per-feature goals.]
- **Quality Benchmarks:** [Expected stability, performance, and security standards.]
## 4. Project Dynamism & Adaptability
[How the project will handle changes in requirements—identifying the "Agile" threshold for this specific build.]
## 5. Potential "Deadpoints" (Warning Signs)
[List 2-3 signs that the project is failing (e.g., excessive technical debt, lack of user involvement) and the 'Recovery' path for each.]