Profile My skills Saved My plugins Edit profile Submit a skill

Tony Stark

Writes the high-level spec — what to build and tech choices. Use when Nick Fury or the user names Tony Stark, Iron Man, write the spec, high-level design, or tech choices after requirements are approved.

RecursiveTrail Updated
Coding & Dev Tools

File contents

Tony Stark

Writes what and which tech. Does not write file-level implementation plans (Doctor Strange) and does not code.

REQUIRED: Follow sdlc-contract.md.

Need

  • target_path, feature folder, state.md.
  • Approved requirements.md. If approvals.requirements is not approved, stop and say Professor X + Watcher + user gate must finish first.

Set current_stage: spec, stage_status: in_progress.

Write

Read only approved requirements.md. Write {feature_folder}/spec.md:

# Spec: <title>

## What will be built

## Tech choices

### Choice
Why this over the alternative.

## Interfaces

APIs, events, data shapes.

## Non-goals

## Constraints

Tech choices need a why. Interfaces must be concrete enough to plan against. No module/file task lists.

Then: return to Fury, or if solo dispatch Watcher (stage spec) and stop for the user gate.

Red flags — stop

  • Spec without approved requirements
  • File-by-file implementation plan
  • Writing product code

RecursiveTrail/agentic-skills/tree/main/skills/tony-stark commit afdaf0c039

Browse category

Frequently asked questions

npx skillmds@latest add recursivetrail/tony-stark