i-have-adhd vs Youkti: Features, Pricing & Which Is Better (2026)
A side-by-side comparison of i-have-adhd and Youkti — features, pricing, and ideal use cases — to help you decide which AI tool fits your workflow.
i
i-have-adhd
ayghri
Coding-agent skill that forces action-first, numbered answers — kills the 'Great question! Let me think...' preamble in Claude Code, Codex, and friends.
Key features
- Action-First Output Rule: Every response leads with the next concrete action instead of preamble.
- Numbered Multi-Step Tasks: Coding tasks come back as numbered lists capped at 5 items each.
- Preamble & Closer Suppression: Eliminates 'Great question!', 'Hope this helps', and other filler.
- Specific Time Estimates: Forces the agent to answer with minutes rather than vague 'a bit' phrasing.
- One-Command Install: /i-have-adhd in Claude Code, $i-have-adhd in Codex, or persistent activation via ~/.claude/.i-have-adhd.
- Auto-Update in Claude Code: Claude Code fetches the skill from GitHub and keeps it up to date — no local clone needed.
- Multi-Language Skill Docs: README available in English, Simplified Chinese, Japanese, Korean, Vietnamese, and Portuguese (BR).
- Fork-and-Tune: Copy skills/i-have-adhd/SKILL.md, edit the 10 rules to taste, restart the agent, and re-invoke.
Best for
- Reduce Preamble Fatigue: Developers who lose time scanning past 'Great question!' openings get straight-to-the-point agent output.
- ADHD-Friendly Workflow: Neurodivergent developers get responses formatted the way their attention can actually consume.
- Terminal-First Sessions: Users driving Claude Code or Codex from a terminal want short, numbered instructions rather than essays.
- Team Style Standard: Teams adopt the skill so every developer's coding agent responds in the same terse format.
- Custom Response Rules: Fork the SKILL.md and hand-tune the 10 rules to fit an internal engineering culture or accessibility need.
Youkti
Youkti AI
Agentic outbound platform that turns account signals and relationship data into prioritized plays, personalized sequences, and pipeline actions.
Key features
- ARYA conversational play builder: Describe an outbound play in plain English and ARYA assembles the signal triggers, persona filters, outreach rules and cadence, updating the live config as you talk
- Signal detection: Tracks funding rounds, hiring surges, leadership changes and transformation initiatives across target accounts and surfaces them on the account record
- Daily Cockpit: A single morning screen that ranks accounts needing attention, overlays the relevant signals, matches the persona and drafts the sequence hook for one-click push
- Account memory: Keeps a continuous record of contacts, last-touch dates and engagement by business unit so context survives rep turnover and long sales cycles
- Deal-risk intelligence: Flags opportunities that are stalling and explains why, with competitor presence and the objections buyers raised
- ICP scoring: Scores accounts against an ideal-customer profile to prioritize high-intent targets over volume-based lists
- Meeting preparation: Builds stakeholder maps, surfaces unresolved questions and recommends talking points ahead of strategic conversations
- MCP interface: Exposes account knowledge and platform actions over MCP so other agentic tools can query and act on the same data
Best for
- An SDR team running signal-triggered outbound instead of static lists, launching sequences only when a funding round or hiring surge indicates timing
- A sales leader reviewing which enterprise deals are at risk before they quietly slip out of the quarter
- An AE reactivating dormant accounts after a new signal such as a digital transformation initiative appears
- RevOps building a new GTM play conversationally rather than configuring a multi-step workflow builder
- An account manager preparing for a renewal by reviewing engagement across business units and mapping new stakeholders
- A CRO reviewing top competitors and recurring objections across the pipeline to adjust messaging