steering

Generates requirements, design, and tasklist steering files for feature implementation workflows.

Updated Jul 1, 2025
One-click install
npx skills add https://github.com/mosakuzii0216/mosaku-v1 --skill steering-mosakuzii0216
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: steering
Source: https://github.com/mosakuzii0216/mosaku-v1/tree/main/.claude/skills/steering
Command: npx skills add https://github.com/mosakuzii0216/mosaku-v1 --skill steering-mosakuzii0216

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It standardizes how features are specified, designed, and tracked by generating structured steering files (requirements.md, design.md, tasklist.md) and enforcing implementation discipline with checklists and retrospectives. ## Core Features & Use Cases - Steering File Generation: Creates requirements, design, and tasklist documents from templates in three separate modes matching a phased /add-feature workflow. - Implementation Management: Enforces tasklist-driven development with MUST/NEVER rules plus NestJS and React checkpoints (Prisma, JWT guards, React Query, Zustand). - Retrospective Recording: Appends a structured post-implementation reflection section to the tasklist capturing plan-vs-actual gaps and lessons learned. - Use Case: When adding a new feature to a NestJS + React app, generate requirements.md first, get approval, then generate design.md and tasklist.md, and track every task to completion. ## Quick Start Ask the assistant to generate a requirements.md steering file for a new feature using the steering skill templates.

Frequently Asked Questions about steering

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

FAQPage Schema
How do I create a requirements document for a new feature?

Use mode 1a to generate requirements.md from the provided template into .steering/{date}-{feature}/. It reads CLAUDE.md for project conventions and reflects brainstorm.md context, with concrete acceptance criteria and explicit out-of-scope items.

How to manage feature implementation with a tasklist?

Mode 2 enforces tasklist-driven development: always reference tasklist.md, mark tasks [x] when done, append newly discovered tasks, and never finish with incomplete tasks. Tasks should be split into units completable within 30 minutes.

Does this workflow support NestJS and React projects?

Yes, it includes specific checkpoints for NestJS backends (Module registration, class-validator DTOs, JwtAuthGuard, Prisma generate) and React frontends (React Query for server state, Zustand for client state, API_BASE_URL usage).

What is the difference between requirements.md, design.md, and tasklist.md?

requirements.md defines what to build with acceptance criteria, design.md specifies architecture, Prisma schema changes, and API endpoints, and tasklist.md breaks work into phased checkbox tasks. Each is generated in a separate mode after the previous is approved.

When should I record an implementation retrospective?

Record the retrospective after all tasks are complete by appending the reflection section to tasklist.md. It captures plan-vs-actual differences, newly required tasks, technical learnings, and improvement proposals for future features.