implement-staff

Implement new modules and public interfaces anchored to a spec.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/chughtapan/safer-by-default --skill implement-staff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-staff
Source: https://github.com/chughtapan/safer-by-default/tree/main/skills/implement-staff
Command: npx skills add https://github.com/chughtapan/safer-by-default --skill implement-staff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Staff implements new architectural territory by introducing new modules, new public interfaces, and new dependencies strictly traced to the spec, ensuring no spec revisions and maintaining discipline.

Core Features & Use Cases

  • Creates new modules and public surfaces anchored to spec lines.
  • Enforces traceability, boundary schemas, and explicit error channels for all new work.
  • Ensures spec-aligned dependency management within the approved plan.

Quick Start

Provide a sub-issue aligned to a published spec and follow the staff workflow to implement the requested architectural surface.

Frequently Asked Questions about implement-staff

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

FAQPage Schema
How do I implement new modules and public APIs strictly from a spec?

To implement new modules from a spec, you need a disciplined workflow that creates architectural surfaces, exports public interfaces, and pins dependencies directly to spec lines to preserve full traceability.

What is spec traceability when adding new architectural surfaces?

Spec traceability is the mechanism of anchoring new modules and public interfaces directly to published spec lines, ensuring all code changes remain strictly bound to the approved architectural plan without deviation.

How do I enforce boundary schemas and typed errors for new public APIs?

You enforce boundary schemas and explicit error channels by applying a disciplined implementation workflow that creates new modules within the target package and exports a public API with an anchored surface.

Do I need a sub-issue and a plan to implement new architectural surfaces?

Yes, implementing new architectural surfaces requires a sub-issue aligned to a published spec and an approved plan to ensure spec-aligned dependency management and prevent unauthorized spec revisions.

Best way to prevent spec revisions when shipping new dependencies?

The best way to prevent spec revisions is using a workflow that strictly anchors new dependencies and public interfaces to the existing spec, ensuring all new architectural territory remains traceable.