Advise Project Approach

What it does

• Picks the right mode: pre-build strategy when no repo exists, mid-build course correction when work is underway, post-build review when the project is nearly done.
• Asks before assuming: for vague requests it fires one concise intake batch (max 7 questions on users, core workflow, stage, budget, deployment target, priorities) and stops.
• No recommendation without receipts: it inspects local evidence, normally two comparable real-world projects, official docs, and official pricing/limits pages, then reports an explicit evidence status of what was and wasn't checked.
• Refuses popularity as a proxy: never picks a stack because of star counts; every choice is tied to real constraints like team skill, timeline, cost, and operational complexity.
• Operating-cost reality check: separates development, launch, and steady-state cost; "free to start" marketing is not accepted as proof.
• Falsifiable output: at least one credible alternative, the conditions that would make the advice wrong, ordered next actions, plus observable acceptance behavior and a focused check for the first step.
• Safety rails: repo review is read-only by default; installing dependencies or running tests/builds/scripts requires permission; .env, keys, and secret files are only reported as existing, never printed.

Who it's for

• Developers choosing a stack and architecture before starting a new product or side project.
• Solo builders and small teams mid-build who need to decide what to keep, change, or defer.
• Teams preparing to launch who want architecture, security, and deploy readiness benchmarked against mature comparables.
• Anyone whose stack choice hinges on managed-service or AI API pricing.

Examples

1. "I want to self-host a document search app solo — what stack fits?" → intake questions, comparable research, then a constraint-fit recommendation that may reject the generic Next.js + Postgres answer.
2. "Review this repo" → reads README, manifests, entry points, CI, and deploy config without executing anything, and reports what was mapped, sampled, and skipped.
3. "Direction is settled — give me the first three steps" → narrow-advice route returns exactly three steps, each with acceptance behavior and a focused check.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/AaravKashyap12/advise-project-approach/HEAD/skills/advise-project-approach/SKILL.md

What I want: (describe your task here)

Install the skill I found on Claude Skill Mart.
Copy the skills/advise-project-approach folder from the GitHub repo AaravKashyap12/advise-project-approach into my ~/.claude/skills/advise-project-approach/.
When it's done, tell me in one line what this skill can do.