implementing-typescript-feature

Orchestrate TypeScript feature implementation across specs, testing, coding, and review.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill orchestrates autonomous TypeScript feature implementation by coordinating specs, testing, coding, and review to ensure cohesive delivery across multiple stories within a feature.

Core Features & Use Cases

  • Autonomous feature implementer coordinating stories through specs, testing, coding, and review.
  • Enforces a strict sequential workflow and Full BSP path usage to maintain traceability and consistency.
  • DRY constants pattern, behavior-driven development, and mandatory review gates to ensure quality and reliability.

Quick Start

Given a feature with stories to implement:

  1. Identify the next incomplete story by listing the feature directory
  2. Run the 5-step implementation cycle
  3. Repeat until all stories are complete

Story → Specs → Test Design → Implement → Review → Remediate → Next Story ↓ ↓ ↓ ↓ ↓ understanding testing coding manual reviewing -specs -typescript -typescript review -typescript

Frequently Asked Questions about implementing-typescript-feature

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

FAQPage Schema
What is the best way to coordinate TypeScript feature implementation across multiple stories?▼

TypeScript feature implementation across multiple stories is orchestrated by coordinating specs, testing, coding, and review in a strict sequential workflow. This enforces traceability and consistency from story specs to final code review.

How do I ensure behavior-first testing during TypeScript feature development?▼

Behavior-first testing in TypeScript feature development is enforced by validating behavior-driven tests immediately after understanding specs and before coding. This ensures test design strictly aligns with expected feature behavior.

Does autonomous TypeScript feature implementation require a specific development environment?▼

Autonomous TypeScript feature implementation requires a TypeScript development environment setup to function. It relies on this environment to coordinate collaboration with design, test, and review skills throughout the workflow.

What are the mandatory review gates in a TypeScript feature workflow?▼

Mandatory review gates in a TypeScript feature workflow require manual review and remediation after coding and before advancing to the next story. This ensures quality and reliability through constant validation.

When should I use a sequential workflow for auto-implementing TypeScript features?▼

A sequential workflow should be used for auto-implementing TypeScript features with multiple stories to maintain traceability and consistency. It enforces DRY constants patterns and mandatory review gates throughout the implementation cycle.