ring-implementing-tasks

Implementing a single planned task (Task N.M.T) end-to-end: selects the right backend agent by language and service type, drives one TDD RED->GREEN turn, then verifies coverage, lint, license headers, runtime, and delivery before handoff. Runs as Gate 0 before ring:reviewing-code. Use to drive ONE task inside an already-running cycle. Skip when asked to implement a whole plan.md or multiple tasks (use ring:running-dev-cycle).

Ir a la instalación

Repositorio: LerianStudio/ring
Última actividad en el origen: 26 de junio de 2026 a las 20:17
Idioma detectado de SKILL.md: inglés
Estrellas: 206
Forks: 26

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/LerianStudio/ring --skill ring-implementing-tasks

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

ring-declaring-plugin-permissions

Interactively authoring an access-manager permission-declaration manifest (permissions.yaml) for the access-manager "inversão de responsabilidade": drives a plugin team through discovering its real Authorize() surface, normalizing every action to the SEMANTIC standard (never HTTP verbs), declaring roles/group grants and the M2M contract, then emits and validates a manifest that matches the lib-auth/v3 auth/declaration schema. Use when a plugin must publish its own permissions at boot (WireFromEnv) instead of the access-manager seed owning them, or when writing/fixing a permissions.yaml. It also bumps the repo's github-actions-shared-workflows CI pin to the release carrying the permission-manifest nudge. Skip when the plugin has no auth guards, or you only need the wiring (see WireFromEnv) and the manifest already exists.

2026-08-11

ring-writing-plans

Writing a rolling-wave phased implementation plan from a spec before coding: a phase-epic-task hierarchy where Phase 1 is detailed into dispatch-ready tasks and later phases stay epic-level for elaboration during execution. Use when a multi-file feature needs decomposition; runs after ring:exploring-codebases or pre-dev gates, hands off to ring:executing-plans or ring:running-dev-cycle. Skip for single-file changes or spikes.

2026-07-02

ring-applying-licenses

Applying or switching a repository's license (Apache 2.0, Elastic License v2, or Proprietary): rewrites the LICENSE file, updates Go/TS source headers, sets SPDX identifiers, and validates consistency after user confirmation. Use when asked to set, apply, or switch a license, or when scaffolding a service with no LICENSE. Skip when license, headers, and SPDX already match, or for non-code repos.

2026-07-02

Ver todos los de este repositorio

name

ring:implementing-tasks

description

Code Implementation (Gate 0)

When to use

Gate 0 of development cycle
Tasks loaded at initialization
Ready to write code

Skip when

Not inside a development cycle (ring:running-dev-cycle or ring:planning-backend-refactor)
Task is documentation-only, configuration-only, or non-code
Implementation already completed for the current gate

Sequence

Runs before: ring:reviewing-code

Complementary: ring:running-dev-cycle, ring:test-driven-development, ring:reviewing-code

You orchestrate. Agents implement. Select the agent, prepare the prompt, track state, validate outputs.

Step 1: Validate Input

The unit of work is a single task (Task N.M.T, e.g. Task 1.1.1) from the phased plan. Its requirements arrive inline from the orchestrator, which reads the task block under its epic in plan.md: Context, Implementation vision, Files, Verification, and Done when.

Task: subagent_type: "{selected_agent}" description: "Gate 0 TDD (RED→GREEN) for {unit_id}" prompt: | ## TDD: write a failing test, then make it pass unit_id: {unit_id} requirements: {requirements} language: {language} service_type: {service_type} Standards: load via state.cached_standards or WebFetch Ring standards for the language. Project rules: {project_rules_path} ## Frontend TDD policy (React/Next.js only) Visual-only components (layout, styling, animations): RED not required — report "Visual-only → RED skipped; visual checks apply in the frontend flow." Behavioral components (hooks, validation, state, conditional rendering, API): RED required. ## Multi-Tenant (Go only) Implement DUAL-MODE from the start. Use resolvers for all resources (tmcore.GetPGContext, tmcore.GetMBContext, etc.) — they work transparently in single-tenant and multi-tenant mode. Load multi-tenant.md for patterns. ## Your task 1. Write a test capturing expected behavior; run it; it MUST fail (no implementation yet); capture the failure output. 2. Implement the minimum code to make the test pass; run tests — all pass. 3. Enforce coverage threshold (Ring minimum 85%, PROJECT_RULES may raise it). 4. Create/update docker-compose and .env.example when the service needs local dependencies. 5. Verify local runtime starts cleanly for the changed service path; verify basic health/observability for the changed code. 6. Write delivery verification results. 7. Commit: "{feat|fix|test|chore}(scope): description". ## Required output - RED: test file path + the actual failure output (MANDATORY — must contain FAIL) - GREEN: implementation files + test pass output - Coverage report (must meet threshold) - Local runtime: docker-compose/.env.example status or explicit "not required" - Basic health/observability verification - Delivery verification: requirements delivered, dead-code check, files changed - Git commit SHA

Language	Service Type	Agent
go	api, worker, batch, cli	ring:backend-go
typescript	api, worker	ring:backend-ts
typescript	frontend, bff	ring:bff-ts

ring-implementing-tasks

Opciones de instalación

Revisa los archivos de origen

Code Implementation (Gate 0)

When to use

Skip when

Sequence

Related

Step 1: Validate Input

Code Implementation (Gate 0)

When to use

Skip when

Sequence

Related

Step 1: Validate Input

Step 2: Validate Prerequisites

Step 3: Gate 0 — TDD (RED → GREEN)

Step 4: Gate 0 Exit — Delivery Verification

Step 5: Commit

Output Format

ring-implementing-tasks

Datos de origen

Opciones de instalación

Revisa los archivos de origen

Más de este repositorio

Más de este repositorio

Code Implementation (Gate 0)

When to use

Skip when

Sequence

Related

Step 1: Validate Input

Code Implementation (Gate 0)

When to use

Skip when

Sequence

Related

Step 1: Validate Input

Step 2: Validate Prerequisites

Step 3: Gate 0 — TDD (RED → GREEN)

Step 4: Gate 0 Exit — Delivery Verification

Step 5: Commit

Output Format