skills.rest
Srain021
Srain021COMMUNITY
Explore all skills by this author →
GitHub

kestrel-mcp-role-backend

Execute RFC workflows using WRITE, REPLACE, APPEND, and RUN indicators.

Updated Apr 23, 2026
Search Tags:#backend#execution#engineering#guidelines#rfc#role
One-click install
npx skills add https://github.com/Srain021/KesTREL --skill kestrel-mcp-role-backend
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kestrel-mcp-role-backend
Source: https://github.com/Srain021/KesTREL/tree/main/.cursor/skills-cursor/kestrel-mcp/roles/backend-engineer
Command: npx skills add https://github.com/Srain021/KesTREL --skill kestrel-mcp-role-backend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Backend Engineer role provides a disciplined persona to execute RFCs without invention, ensuring consistency and adherence to established indicators.

Core Features & Use Cases

  • Enforces adherence to WRITE/REPLACE/APPEND/RUN during RFC execution.
  • Segregates RFC execution from authoring to prevent scope drift and miscommunication.
  • Useful for engineering teams requiring strict procedural compliance and traceable decisions.

Quick Start

Activate the Backend Engineer role and begin executing RFCs by following the WRITE/REPLACE/APPEND/RUN indicators exactly.

Frequently Asked Questions about kestrel-mcp-role-backend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute an RFC workflow without scope drift?▼

Executing an RFC workflow without scope drift requires a disciplined backend engineering persona that strictly adheres to procedural indicators like WRITE, REPLACE, APPEND, and RUN, segregating execution from authoring.

What are WRITE, REPLACE, APPEND, and RUN indicators in RFC execution?▼

WRITE, REPLACE, APPEND, and RUN are strict procedural indicators governing RFC execution. They ensure a backend engineer follows exact operational steps without invention, maintaining traceable decisions and procedural compliance.

When do I need to segregate RFC execution from RFC authoring?▼

Segregating RFC execution from authoring is necessary when engineering teams require strict procedural compliance and traceable decisions, preventing miscommunication and scope drift during backend implementation.

Can I use this disciplined backend role for RFC tasks without strict indicators?▼

This backend role is designed for RFC execution scenarios governed by strict indicators. Without established WRITE, REPLACE, APPEND, or RUN rules, the procedural adherence and boundary enforcement it provides may not apply effectively.

What is the best way to ensure consistency when executing RFCs across an engineering team?▼

Ensuring consistency when executing RFCs across an engineering team involves adopting a disciplined backend engineer persona that applies strict procedural indicators and prevents invention during implementation.

Does RFC execution with this backend role handle RFC authoring tasks?▼

RFC execution with this backend role does not handle RFC authoring tasks. It strictly segregates execution from authoring to prevent scope drift and ensure adherence to established indicators.

Related Skills

Explore More Software Engineering Skills→
SebastianBoehlerSebastianBoehler

agentedit-cli

Apply deterministic file edits from JSON or YAML specs.

Community
Intermediate
tunneleventunneleven

c4flow:pr-review

Process pull request comments and push code updates iteratively.

Community
Intermediate
spiral-app-labsspiral-app-labs

nina-binky-in-app-resource-writing

Draft empathetic in-app resource articles for new parents in the Binky app.

Official
Intermediate
akillnessakillness
40

microsoft-agent-framework

Define role-based workflows with auditable execution for multi-agent orchestration.

Community
Advanced