This skill should be used when the user asks to "build a dev team lineup", "create dev team lines", "dev team game plan", "dev team strategy", "optimize dev team line combinations", "set up dev team special teams", "plan dev team absences", "update dev team playbook", "update dev team roster", "update dev team power…
Interview the user relentlessly about a technical design or architecture until every major decision is examined, justified, and stress-tested. Use when the user wants to pressure-test a system design, validate an architecture, compare options, or mentions "grill me" in a technical context.
Run an adversarial debate with a cross-model reviewer (Codex or Antigravity/agy) to stress-test a draft, plan, research claim, or design decision. Use this whenever you need structured critique before finalizing decisions.
Produce higher-quality code by breaking a feature into small, focused tasks the coding agent can nail one at a time. Works like an engineering team: feature → milestones (product deliverables) → 30-min tasks with specific files, acceptance criteria, and dependencies. Each task runs in a fresh context — narrow scope…
A workflow for developing one requirement across multiple Git repositories, which are separate code projects. It creates a shared workspace containing the requirement, implementation plan, and selected project copies.
Plan a feature - gathers context, researches, interviews, identifies risks, outputs PRD. Use when: user says autoplan, /autoplan, or wants to plan a feature with the full research-interview-premortem workflow.
Use when refining the scope, audience, reader takeaways, hooks, evidence plan, examples, code snippets, benchmark/performance claims, narrative angle, or outline for a blog post before drafting. Trigger for requests to clarify what a post should be about, who it is for, what readers should learn or believe, how to…
A project-context setup tool for creating lasting guidance about a new repository. It can cover software, research, data science, web, systems, and mobile projects.
Facilitate a skeptical multi-member AccordAgents discussion that ends in one agreed resolution approved by every selected member. Use only when User explicitly wants an accord, multi-member consensus, cross-checking by named members, or a resolution approved by multiple agents. Do not use for an ordinary single-agent…
A tool that turns a product owner's request into a YAML task file for a software manager. YAML is a human-readable format for structured settings and instructions.
Feasibility study report writing guide for project-level decision support. Use when user asks to write a feasibility study, feasibility analysis, project feasibility report, or investment feasibility assessment. Covers healthcare, data services, smart agriculture and other domains. Includes report templates…
Generate a complete demo preparation package for an upcoming meeting. Use when the user has a demo, discovery call, or sales meeting coming up and needs to prepare. Researches the prospect, generates talking points, SPIN questions, objection handling, and email templates — all personalized to the user's product.
Plan an Odoo module version upgrade (e.g. 16.0 to 19.0, 17.0 to 19.0) by first checking the Odoo Apps Store for a free ready-made replacement, then auditing the manifest, models, views, data records (cron/server actions), security, SCSS/CSS and JS on two axes — what changed upstream in the real odoo/odoo and…
Act as the architectural brain of a multi-agent engineering operation — investigate an unfamiliar, large, or legacy codebase, model how it really works, diagnose root causes instead of symptoms, design the minimal architecturally-correct change, decompose it into scoped task contracts with a dependency DAG, persist…
CFAR rationality technique for installing reliable automatic behaviors by pairing specific triggers with specific actions. Based on implementation intentions research (0.65 SD effect size). Use when the user: (1) wants to build a new habit or change a behavior, (2) knows what they should do but keeps forgetting or…
Use when building software with AI agents and you need a serious end-to-end workflow instead of vibe coding. Covers harness choice, context discipline, cleanup, review loops, launch pressure, and security basics.
A Chinese-language planning assistant for marketing directors. It guides annual business planning through market analysis, competitor strategy, goals, budgets, execution, and review.
A long-running research workflow for topics with measurable results. It repeatedly tests a hypothesis, scores the attempt, records lessons, and can continue through an automated loop.
A Chinese-language business analysis adviser covering common strategy, marketing, business-model, organisation, and problem-solving frameworks. Frameworks are structured methods such as SWOT, PEST, the 4Ps, and the business model canvas.
Granular implementation plan with ordered tasks and typed architectural anchors. Acts as Software Architect to define HOW, WHERE, and in what ORDER. Reads spec from docs/specs/ or accepts inline description. Produces tasks of 2-5 min each with exact file paths, typed signatures (interfaces, function contracts)…
The central source of truth for planning, tracking progress, and orchestrating work between the AI Agent and the User in this codebase.
★not rated 5 3mo agoA35 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: