Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By parhumm
Orchestrate a spec-to-ship workflow: generate PRDs, API contracts, backend/frontend code, tests, and CI/CD from requirements, then audit quality, security, and design consistency — all within a multi-role AI pipeline with human approval gates.
npx claudepluginhub parhumm/jaan-to --plugin jaan-toYou are a context scout for jaan.to plugin skills.
You are a quality reviewer for jaan.to plugin outputs.
You are a visual review assistant. Your job is to review component code for quality without requiring browser automation.
Generate OpenAPI 3.1 contracts with schemas, RFC 9457 errors, versioning, and examples. Use when defining API contracts from entities.
Generate data model docs with tables, constraints, indexes, retention, and migration notes. Use when designing database schemas from entities.
Review backend PRs for security, performance, code quality, and testing gaps across any stack. Use when reviewing backend pull requests.
Generate production-ready backend code with routes, data models, service layers, and validation. Use when scaffolding backend from specs.
Generate service implementations with business logic from specs and scaffold stubs. Use when implementing backend services.
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Production-ready Claude Code configuration with role-based workflows (PM→Lead→Designer→Dev→QA), safety hooks, 44 commands, 19 skills, 8 agents, 43 rules, 30 hook scripts across 19 events, auto-learning pipeline, hook profiles, and multi-language coding standards
Structured project planning and execution through brainstorm, spec, and build phases across three execution tiers: sequential, delegated sub-agents, and full agent teams
12 PM-specific agent skills, 6 workflow commands, 3 automation hooks for Product Managers
Plugin de ingeniería de software completa: 10 agentes de núcleo y 9 opcionales con personalidad propia, memoria persistente por proyecto, quality gates y flujos automatizados desde la idea hasta producción.
Helder's personal SDLC toolbelt for AI coding agents — from PRD to ship. Bundles the tracer-bullet workflow alongside TDD, code review, audits, and shipping skills.
Provider-agnostic skills for autonomous product development: spec, task, implement, test, review, and summarize changes.
Uses power tools
Uses Bash, Write, or Edit tools
Uses power tools
Uses Bash, Write, or Edit tools
Has parse errors
Some configuration could not be fully parsed
Has parse errors
Some configuration could not be fully parsed
Share bugs, ideas, or general feedback.
AI-powered skills for PM, Data, QA, Dev workflows. PRD generation, GTM tracking, documentation management, and more.
| Component | Count | Description |
|---|---|---|
| Skills | 56 | PM, Dev, Backend, Frontend, QA, UX, Data, Detect, WordPress, Release, Security, DevOps, Core |
| Agents | 3 | quality-reviewer, context-scout, visual-reviewer |
| Hooks | 7 | Setup, SessionStart, PreToolUse, PostToolUse, Stop, TaskCompleted, TeammateIdle |
| Output Styles | 2 | enterprise-doc, concise-summary |
"Jaan" is a Persian word meaning "soul" or "life." When you say "jaan-e man" — "my soul" — you're expressing the deepest form of care.
Jaan.to means "giving soul to something" — a person, a project, a product. It's the act of breathing life into work that would otherwise feel mechanical.
claude
/plugin marketplace add parhumm/jaan-to
/plugin install jaan-to
/jaan-init
# One-command installer (recommended for end users)
bash <(curl -fsSL https://raw.githubusercontent.com/parhumm/jaan-to/main/scripts/install-codex-skillpack.sh)
# Fallback if you're in this repo locally
bash ./scripts/install-codex-skillpack.sh
Then:
/jaan-init once./skills, /jaan-to:*, /jaan-init, or native $skill mentions.Examples:
/skills
/jaan-init
/jaan-to:pm-prd-write
$pm-prd-write
In Codex, /jaan-to:* and /jaan-init are intentionally preserved as aliases for native $skill.
Development version:
claude
/plugin marketplace add parhumm/jaan-to#dev
/plugin install jaan-to
/jaan-init
Switch stable/dev:
/plugin uninstall jaan-to
/plugin marketplace add parhumm/jaan-to # stable
/plugin marketplace add parhumm/jaan-to#dev # dev
/plugin install jaan-to
/jaan-init
Check installed version:
/plugin list
# Claude local dev
claude --plugin-dir /path/to/jaan-to
# Build both runtime targets
./scripts/build-all-targets.sh
# Build Codex skillpack source
bash ./scripts/build-codex-skillpack.sh
# Skillpack drift guard
bash ./scripts/validate-codex-skillpack.sh
# Skill PR prep (regenerate + validate + stage skillpack)
bash ./scripts/prepare-skill-pr.sh
# Integrated dual-runtime smoke
bash scripts/test/e2e-dual-runtime-smoke.sh
./scripts/build-target.sh codex
cd ./dist/jaan-to-codex
./jaan-to setup /path/to/your-project --mode local
setup --mode auto resolves to global if ~/.agents/skills/jaan-to-codex-pack exists, otherwise local.
auto method SSL failure:
--method git.$skill ambiguity from duplicate names:
.agents/skills/<jaan-to-skill> entries and use global mode.Claude Code installation, command namespace (/jaan-to:*), and plugin behavior remain unchanged.
Codex support is added as a thin adapter and runner layer without changing Claude runtime contracts.
The bootstrap hook automatically creates jaan-to/ in your project with:
context/ — Config and boundary templates (customize for your project)templates/ — Output templates for each skilllearn/ — Learning seeds (improve over time)outputs/ — Generated outputs (PRDs, tracking code, research, etc.)docs/ — Reference docs (style guide, skill spec)./scripts/verify-install.sh /path/to/your-project
jaan.to follows Claude Code best practices by NOT shipping with configuration files. All settings are OPTIONAL and should be added to YOUR project's .claude/settings.json if needed.
Why? Configuration is project-specific, not plugin-specific. This keeps the plugin portable and ensures you maintain full control over permissions and environment variables in your own codebase.
See Recommended Permissions below for examples of common permission patterns.