project-init
🔌PluginMoxyWolfLLC/moxywolf-plugins
|Cowork project lifecycle for MoxyWolf projects. /init-project scaffolds tailored Project Instructions. /session-start auto-resolves the project — explicit argument, then launch directory, then the most recently active project, never a picker — mounts the three standard roots, reads the previous session's handoff (cross-checked against current team-shared memory so stale procedural reminders get flagged STALE rather than silently propagated), reads Taskade/_Shared Files/_shared-memory/INDEX.md and surfaces it as a 'Team-shared rules in effect' briefing section, and probes the team-shared OpenRouter key (DR-010). /session-end asks who authored the handoff and whether it's a baton-pass, writes the canonical handoff with `author` / `for` frontmatter, requires every general behavioral reminder in the procedural-reminders section to cite a currently-existing team-shared memory file (or be tagged session-specific), supports --author / --handoff-to / --solo, refreshes each writable repo's README.md, then runs /obsidian-update. /init-project saves the full instructions on disk as the single source of truth and pastes only a thin loader stub (mounts + file-write-path override + read-the-file-first imperative) into Cowork settings, so the embedded copy never drifts out of sync with the on-disk file (DR-010). The stub skeleton and on-disk reconciliation directives live in a vault spec that both /init-project and /refresh-project-instructions read at run time, so changing a project-instruction rule is a vault edit plus a per-project /refresh-project-instructions run, never a plugin update. v0.22.0: folder access is fully mode-agnostic across online (cloud) and offline (on-computer) — each capability is detected by tool presence with a filesystem-probe fallback (detect via get_device_info or by listing the path; mount via request_cowork_directory when present, else prompt Add folder; pick via native picker when present, else device_list_dir + AskUserQuestion chips), so nothing hard-depends on request_cowork_directory and the skills run identically online or offline. v0.23.0: task-board reads moved from the retired vault kanban (KANBAN_VIEW.md) to the team Jira board (project MOXY) — /session-start Step 4b queries MOXY via the Atlassian MCP, strictly filtered fail-closed to the project's Jira label (project-<slug>); the 'Kanban project tag(s)' field now denotes a Jira label.
Part of
MoxyWolfLLC/moxywolf-plugins
Installation
/plugin marketplace add MoxyWolfLLC/moxywolf-plugins/plugin install project-init@moxywolf-pluginsMore from this repository10
Marketplace
Framework-specific development best practices for React, Next.js, Supabase/Postgres, TDD, and Playwright E2E testing.
Steph Ango / Obsidian's five official agent skills vendored into the MoxyWolf marketplace so every team Mac gets consistent Obsidian fluency. Ships obsidian-markdown (proper wiki-link / callout / embed rendering), obsidian-bases (Obsidian's new Bases query syntax that replaced Dataview for most use cases), json-canvas (the JSON Canvas spec for visual boards), obsidian-cli (script-friendly Obsidian invocation), and defuddle (Defuddle HTML-to-Markdown cleanup for web clips). Upstream: kepano/obsidian-skills, Apache-2.0. v1.0.0.
Generate MoxyWolf monthly board deck from LivePlan, GA4, Taskade, and GitHub data.
/marcom-best-practices [target] finds and applies best practices for any MARCOM project, idea, channel, or campaign, on the premise that we're probably doing it wrong and should consult the full toolbox before changing direction. Classifies the target into 13 MARCOM domains (lifecycle email/outreach expanded into onboarding -> nurturing -> upgrade -> retention, not one bucket), then sweeps three tiers: our installed plugins/skills via a curated domain->skill capability map; the Workforce Automation Supabase catalog of ~580K catalogued Claude skills/plugins/MCPs (with an 'installed' source for a real have/don't-have diff) to surface adoption candidates we don't have; and heavy external web research. Benchmarks current MoxyWolf practice against all three using live analytics (GA4/PostHog/Ahrefs/CRM), writes a prioritized best-practices brief to the target's MARCOM folder, lists adoption candidates, and auto-runs the top applicable installed skills to produce starter deliverables.
Jira (project MOXY) is the single canonical task board. Sweeps non-chat sources (Google Drive Active Tasks, Google Calendar, Gmail) for genuinely-new action items, dedups them against the board (open + recently-Done), and files them to MOXY with best-practice issue authoring (Context/Acceptance/Notes descriptions, sub-items as real Subtasks, dependencies as Blocks links, Backlog default), then maintains board hygiene (priorities, column limits, In Review reviewer pairings). v0.6.0 retired the vault kanban and all Slack task flows (no Obsidian source-of-truth, no dual-authority sync-back, no Slack scraping, no #general digest) — team members file their own tickets directly in Jira, including from Slack via the Jira Slack app. Bulk writes to the shared tracker stay human-gated.
Six vault-* workflow skills vendored from az9713/claude-code-obsidian. Companion to obsidian-skills (kepano's foundational five) — those handle the file formats, these run the daily vault workflows: vault-capture (quick-drop into _inbox/), vault-save (structured save to the right folder), vault-journal (Daily Journal/YYYY-MM-DD.md authoring), vault-synthesize (multi-note synthesis with citations), vault-moc (Map-of-Content authoring), vault-health (orphan / broken-link / stale-tag audits). v1.0.0.
Standalone graphify knowledge-graph runner with Obsidian integration. Graph any corpus — a code directory via /graphify, a Supabase database via /graphify-supabase (native --postgres introspection preferred, MCP corpus emit fallback), or the Obsidian vault itself via /graphify-vault (docs-first keyed flow). Obsidian-format exports land back in the MoxyWolf Vault (Projects/<project>/06-Engineering/graphs/ per project, _Shared Knowledge/Vault Graph/ vault-wide) so they cross-link with real notes. Hosts the canonical graphify-core runner protocol (team OpenRouter key per DR-010, two-pass AST-then-label sandbox-safe split, keyless fallback); github-repo-analyzer delegates its Step 0 here.
End-to-end SaaS and API gateway pricing research, modeling, and copywriting. Combines competitor intelligence, pricing frameworks (Van Westendorp, Gabor-Granger, value-based), and conversion-optimized pricing-page generation.
Build and enrich BibTeX bibliographies with AI-generated abstracts from URLs or uploaded .bib files.