skills.rest
chughtapan
chughtapanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

implement-junior

Implement a single module's internal bodies per an architected plan.

Updated Apr 18, 2026
Search Tags:#lint#implement#tests#typecheck#junior-dev#architect-plan#module-internals
One-click install
npx skills add https://github.com/chughtapan/safer-by-default --skill implement-junior
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-junior
Source: https://github.com/chughtapan/safer-by-default/tree/main/skills/implement-junior
Command: npx skills add https://github.com/chughtapan/safer-by-default --skill implement-junior

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The task provides a disciplined, plan-driven path to complete a module's internals without changing its public surface, ensuring alignment with architect-approved scope and boundaries.

Core Features & Use Cases

  • Enforces single-module completion against an architected plan.
  • Keeps changes localized to the target module, with validation via tests, lint, and type checking.
  • Use Case: you receive a stubbed module and need to implement the body to satisfy the acceptance criteria while preserving interfaces.

Quick Start

Implement the module internals strictly according to the plan, then run lint, typecheck, and tests before opening a draft PR.

Frequently Asked Questions about implement-junior

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

FAQPage Schema
How do I implement a stubbed module to spec without changing its public interface?▼

You implement a stubbed module by completing its internal bodies according to an architected plan while preserving the public interface. This localized approach ensures boundaries are maintained, validating changes with lint, typecheck, and tests before opening a draft PR.

What is the best way to ensure type safety when filling in module internals?▼

Ensuring type safety when implementing module internals involves using branded types, schema decoding at boundaries, and tagged errors. You validate this safety by running lint, typecheck, and tests against the architected plan.

How do I validate module implementation changes before opening a draft PR?▼

You validate module implementation changes before a draft PR by running lint, typecheck, and tests. This ensures the internal bodies satisfy the acceptance criteria of the architected plan while keeping changes localized to the target module.

Can I modify multiple modules when completing an architected plan?▼

No, you cannot modify multiple modules when completing an architected plan. The process enforces single-module completion, keeping changes localized strictly to the target module's internal bodies without touching additional modules or altering the public surface.

Why do I need schema decoding at module boundaries during implementation?▼

Schema decoding at module boundaries is needed during implementation to ensure data safety when filling in internal bodies. Combined with branded types and tagged errors, it validates data entering the module and enforces architected plan boundaries.

Related Skills

Explore More Software Engineering Skills→
archibatearchibate
6

python-project-structure

Organize Python projects with module boundaries and explicit __all__ interfaces.

Community
Intermediate
avoidthekitchenavoidthekitchen
1

final-audit

Audit a feature's codebase for systemic bugs, security vulnerabilities, and consistency errors.

Community
Advanced
Pact-Community-OrganizationPact-Community-Organization
1

test-generation

Generate REPL test scaffolding and TypeScript devnet suites from Pact module definitions and acceptance criteria.

Official
Advanced
cdalsoniiicdalsoniii

N+1 Query Detection

Detect N+1 query patterns in GORM repository and service code.

Community
Intermediate