Plugins

1 plugin

The shared foundation of the Han suite: the specialist agent roster the other plugins dispatch, the project-discovery skill with its project-scanner agent, and the canonical evidence and YAGNI rule files. The documentation skills live in han-documentation, the pre-planning research skills in han-research, the planning skills in han-planning, and the coding skills in han-coding; each depends on han

2 skills · plugin

Results for “specialist”

6 skills

paw-upwork-agent-coach

Upwork freelance coach and orchestrator for niche discovery, positioning, and specialist routing. Use when the user asks to talk to the Upwork coach, wants to find their freelance niche, build their Upwork presence, figure out positioning, or decide which Upwork specialist to run next. Triggers: 'help me with Upwork', 'find my niche', 'what should my Upwork profile say', 'Upwork coach', 'position myself on Upwork', 'I keep losing jobs on Upwork'.

srednoff888-art

product-manager-agent

Agent profile for prioritize product scope, user outcomes, MVP slices, roadmap tradeoffs, and launch criteria. Use when Codex needs a specialist agent perspective for planning, implementation, review, debugging, validation, or handoff in this domain.

More results

paw-ps-software-executor

Product execution specialist for SaaS, apps, AI tools, and internal software products. Trigger when user requests 'build SaaS', 'define features', 'create user flow', 'scope MVP', 'prepare build package', 'software product', 'app definition', or 'PRD creation'.

Expert en biotechnologies avancées (bioinformatics, genomics, CRISPR, drug discovery, DZ research)

paw-ps-audience

Customer insight specialist for audience understanding. Use when defining target audience, buyer personas, customer pains, value mapping, problem discovery, audience language. Triggers: 'who would buy this', 'target audience', 'buyer persona', 'customer pain points', 'ideal customer', 'user problems', 'value proposition', 'audience research'.

theheavenlyd3mon

Use when asked to fix, build, refactor, review, verify, or release software and the work is non-trivial — including delivering a change request (issue, ticket, or request) from intake through planning, gates, implementation, review, verified PR, and authorized post-merge release. neckbeard routes the change through framing, discovery, design, implementation, review, verification, delivery, and learning — choosing the smallest *safe* intervention, proving it at the real delivery boundary, and leaving an inspectable evidence ledger. For change-request / issue-to-PR work, conditionally loads a 9-phase journey with gates, delivery packet, and lifecycle integration. Composes specialist catalog skills rather than replacing them. Not a persona, not a '10x developer' prompt, not a LOC-minimizer. The journey is not loaded for plain fixes, refactors, or reviews that lack an issue/ticket trajectory.