Takkuya·Takkuya/claude-skills/feature-discovery/SKILL.md

feature-discovery

Skill0 starsChanged 3 months agoNo licenceView on GitHub

Pre-plan discovery workflow for features whose viability depends on third-party integrations, platform policies, or unfamiliar constraints — reads product specs, scopes the codebase (monorepo-aware), runs deep parallel research per named integration to surface real limits/quotas/gotchas, reads the current state of the relevant code, then dispatches an adversarial panel that tries to break the proposed approach along three lenses (constraints & policy, edge cases & failure modes, alternatives & prior art). Produces a `.discovery/<slug>/discovery.html` decision artifact that captures constraints, weighed architecture options, surfaced edge cases, and open questions — NOT a build plan. Use this whenever the user has a feature idea that involves external integrations (Stripe, RevenueCat, IAP, Firebase, Supabase, AI providers, payments, auth, etc.), platform-specific rules (App Store / Play Store policies), or an architecture they aren't yet sure will hold — including "/feature-discovery", "vamos descobrir se essa feature funciona", "quero pressure-testar essa ideia", "que restrições X tem?", "que edge cases eu não vi nessa feature?", "quais as gotchas de integrar com X", "let's pressure-test this feature", "what constraints does X impose", or "help me argue against this approach before I commit". This runs BEFORE `plan-phases` — its output feeds the plan when the user commits to a direction. Do NOT use for bug fixes, small tweaks, or features where the architecture is already settled — for those, go straight to `plan-phases` or just do the work.