AIFLC (AI Full Life Cycle) PDLC (Product Development Life Cycle) Family — 11 injectable workflow packages that guide AI coding agents through professional software delivery: idea evaluation → project initiation → portfolio governance → product ownership → UX design → architecture → workspace generation → compliance →…
A product-development guide for building software for real users rather than only making code run. It helps decide how much attention to give user needs, product usefulness, error handling, documentation, and release risk.
Run a substantive idea, draft, design, architecture, strategy, or decision through a modular Council → Chair → Executor → Reviewer workflow. Use when the user asks to council, develop, pressure-test, stress-test, poke holes in, strengthen, review, synthesize, create an implementation plan, or turn a complex set of…
Convene a four-role adversarial council - Believer, Skeptic, Investor, Judge - on a decision, idea, plan, or claim, and issue a ruling with a confidence level, a ranked list of what must be true, and the cheapest test that would falsify it. Use when the user asks whether to build, ship, buy, join, or kill something…
A set of rules for coordinating coding work between multiple AI agents. It turns a request into an agreed plan, defines what counts as success, and supports work that can pause and continue later.
Plan a focused work session before execution begins, inspect current/local open tasks, estimate required time, score feasibility against the actual deadline window, checkpoint progress, resume unfinished sessions, create handoffs, and record private local task memory. Use when the user asks to start, schedule…
A project-status scanner and workflow recommender, described in Chinese, for guiding development work through a ten-step process. It gathers information about Git, progress, specifications, audits, and changes, then proposes a workflow for user approval.
Execute and CLOSE an ExecPlan end-to-end in CueCrux — the execution half that execplan-synthesize/appraise/research (authoring half) hand off to. Runs the milestone loop: claim from the ranked board, announce focus for collision detection, worktree, implement, gate fact, PR, shepherd checks, merge, next milestone…
Runs a Monday-morning review across a portfolio of accounts and produces a single prioritised action list with the reasoning shown. Use when the user says "weekly review", "what should I work on this week", "run my Monday review", or asks what has gone quiet across their accounts. Designed to be run as a scheduled…
A coordination skill for routing complex requests across research, discussion, review, and other roles or providers. A provider is the service that performs a delegated task.
A coordination workflow for managing software tasks across planning, worker agents, testing, auditing, approvals, and configuration governance. It stores task state in structured folders and records each state change in a log.
Audit long, complex, and potentially inconsistent PM taskbooks and compile them into one self-contained, semantically validated Product Brief with a requirement ledger, WP dependency graph, budgets, absolute schedule, gates, tests, experiment evidence, risks, recovery, and stop conditions. Use for long-horizon or…
Onboard a project into this governance layer: scan a repo that was pasted or cloned into Projects/, draft its bible from what the code actually shows, create its tracker and workspace pointer, register it in the composition manifest, and echo the reconstructed setup back for correction. Use this whenever the user…
A planning workflow that breaks a large or unclear task into a hierarchy of plans, from a main problem down to concrete actions for sub-agents. It uses GraphMind to track review, approval, execution, and completion.
Disciplined plan-build-verify loop for implementing a feature or change. Use when building something new or modifying existing behavior, especially across multiple files.
Turn a single Agent into a full multi-perspective meeting. The Agent auto-generates one role-played participant per perspective, runs a structured debate with cross-examination, converges to a conclusion, and outputs an HTML meeting-minutes file. Trigger on any research / analysis / discussion / decision request.
Classify project work into medium, high, or extra-high reasoning effort while keeping high as the stable default. Use when planning or starting a work order, choosing validation scope, handling repeated failures, making architecture or release decisions, controlling reasoning-cost usage, or preventing frequent…
Multi-agent market validation skill. Spawns 6 parallel research analysts (Community uses last30days for fresh 30-day signal; Claim Verifier uses deep-research for fact-checking) and delivers a BUILD / CONDITIONAL / PIVOT / STOP verdict with a 7-pillar scorecard. Use when user says "should I build this", "/sib"…
Run Colla Agent, a traceable bounded collaboration loop in which the current Codex session implements a project and Antigravity plans and reviews it read-only. Use for complex or high-risk coding, design, refactoring, debugging, document, media, data, or multi-file project work when the user asks for Colla Agent…
Critical evaluation of proposed changes BEFORE their implementation. Use when: Need to evaluate proposed changes before implementation Want to reduce merge rejection risk Need to cut scope to minimum valuable change Require pre-implementation quality gate Builds structured JSON with decision (approve/revise/reject)…
Create, rewrite, split, or quality-check Linear issues so each task has an evidence-based problem statement, one executable outcome, explicit scope, falsifiable acceptance criteria, concrete validation, dependencies, and the existing labels required for repository, agent, and reviewer routing. Use when a user asks to…
★not rated 2 1mo agoA91 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: