Menu
SkillsMP has collected 12 skills from affectionatec/agentic-engineering. Open a skill to review its source and details.
Showing 12 of 12 collected skills.
Chain-aware unattended loop driver for the Agentic Engineering suite. Use ONLY when the user explicitly asks to run multiple implementation-plan tasks unattended — "run the loop", "run-loop M2", "work through milestone M2 without stopping", "run the next N…
Entry point and router for the Agentic Engineering suite. Use when starting work in a project that uses (or should use) the documentation chain, when unsure which chain document or skill comes next, or when asked where the project stands. Triggers on "use…
Use when a technical choice has multiple valid options and the decision has lasting consequences, when revisiting or superseding a prior architectural decision, or when about to lock in a technology, pattern, or constraint that will be hard to reverse.…
Use when something said or decided in conversation makes a chain document (PRD, SPEC, ADR, IMPL PLAN, AGENTS.md) stale, contradicted, or incomplete, or when the user proposes a new feature or scope change mid-project. Triggers on "I want to add a feature",…
Use when an existing or legacy codebase needs to enter the agentic-engineering workflow but has no chain documents (or only scattered legacy docs — README, wiki, design notes). Triggers on "onboard this repo", "migrate this project to agentic-engineering",…
Use when specs are approved and work needs to be broken into independently executable tasks, when sequencing dependencies across modules, when sizing milestones, or when a project is about to start coding but lacks a milestone breakdown. Triggers on "let's…
Use when a task or milestone claims completion and must be verified before being marked done, when acting as a verifier sub-agent checking a producer's work, or when a "done" claim needs evidence. Triggers on "verify this task", "is this actually done",…
Use when starting a new project or feature from scratch, when a rough idea needs to be turned into a structured product spec, or when scope, target users, or success metrics are undefined. Triggers on "let's build X", "new project", "kick off", "write a PRD",…
Use at the start of every coding session (read docs/status.md before any other action), at the end of every session (append handoff log entry), or when checking current progress, last-done work, in-flight tasks, or what's blocked. Triggers on session…
Use when the PRD is finalized and precise implementation contracts are needed, when defining API shapes, data models, state machines, error taxonomies, or acceptance criteria, or when ambiguous "handle this gracefully" requirements need to be hardened into…
Use when bootstrapping a new repo for AI-assisted development, when no AGENTS.md / CLAUDE.md / copilot-instructions.md / .cursorrules exists yet, or when consolidating scattered tool-specific config into one source of truth. Triggers on "create AGENTS.md",…
Use when implementation work is about to touch code (branch before the first commit), when a built task needs to ship as a pull request, when defining how branches, commits, and PRs map to plan tasks, or when parallel agents share one repository. Triggers on…