implementing-typescript-feature

Orchestrate TypeScript feature implementation across stories with a strict five-step cycle.

1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/outcomeeng/claude --skill implementing-typescript-feature-outcomeeng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implementing-typescript-feature
Source: https://github.com/outcomeeng/claude/tree/main/plugins/typescript/skills/implementing-typescript-feature
Command: npx skills add https://github.com/outcomeeng/claude --skill implementing-typescript-feature-outcomeeng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Autonomous orchestration for implementing TypeScript features across multiple stories within a feature, ensuring end-to-end alignment of specs, testing, coding, and review in a strict sequence.

Core Features & Use Cases

  • Orchestrates the full 5-step implementation cycle (Understanding specs, Design tests, Implement, Review, Remediate) for each story.
  • Enforces the required sequencing and BSP path semantics to maintain consistent traceability.
  • Integrates with other skills (understanding-specs, testing-typescript, coding-typescript, reviewing-typescript) to progressively complete stories and push for review readiness.

Quick Start

Begin by loading the current story context with the understanding-specs skill and proceed through the mandated 5-step cycle.

Frequently Asked Questions about implementing-typescript-feature

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

FAQPage Schema
How do I orchestrate end-to-end TypeScript feature implementation across multiple stories?

Orchestrate TypeScript feature implementation by coordinating specs, testing, coding, and review in a strict sequence. This ensures proper BSP path usage and deterministic workflow alignment for multiple stories within a feature.

What is the best way to enforce a strict sequence for TypeScript testing and code review?

Enforce a strict sequence for TypeScript testing and review by applying a mandated 5-step implementation cycle: understanding specs, designing tests, implementing, reviewing, and remediating. This ensures proper traceability and mandatory review gates.

Can I integrate understanding-specs and testing-typescript skills within my TypeScript workflow?

Yes, you can integrate understanding-specs and testing-typescript skills within your TypeScript workflow. The orchestration process coordinates these skills to progressively complete stories and push for review readiness.

How do I start the TypeScript feature implementation cycle?

Begin the TypeScript feature implementation cycle by loading the current story context with the understanding-specs skill, then proceed through the mandated 5-step cycle to ensure end-to-end alignment.

Does a deterministic TypeScript workflow require mandatory review gates for each story?

Yes, a deterministic TypeScript workflow requires mandatory review gates for each story. The orchestration enforces strict sequencing to satisfy requirements for inter-skill coordination and proper BSP path semantics.

Why does TypeScript feature implementation require coordinating multiple skills for each story?

TypeScript feature implementation requires coordinating multiple skills to ensure end-to-end alignment of specs, testing, coding, and review. This orchestration maintains consistent traceability and deterministic workflow execution across stories.