Results for “requirements”

Enforce writing specifications before any code, with structured formats, acceptance criteria, and validation to reduce rework and clarify requirements.

Start a new milestone cycle — update PROJECT.md and route to requirements

Interactive feature development workflow from idea to implementation. Creates requirements (EARS format), design documents, and implementation task lists. Use when creating feature specs, requirements documents, design documents, or implementation plans. Triggered by "kiro" or references to .kiro/specs/ directory.

Use when you have a spec or requirements for a multi-step task, before touching code

Use when you have a spec or requirements for a multi-step task, before touching code

Use when you have a spec or requirements for a multi-step task, before touching code

Use when you have a spec or requirements for a multi-step task, before touching code

Use when you have a spec or requirements for a multi-step task, before touching code

Use when you have a spec or requirements for a multi-step task, before touching code

Use when you have a spec or requirements for a multi-step task, before touching code

Validates generated SRS documents against IEEE 830-1998, fixes errors, and reports compliance verdict.

Creates detailed, bite-sized implementation plans from specs or requirements, with exact file paths, code, and TDD steps.

Displays comprehensive project statistics including phases, plans, requirements, git metrics, and timeline.

Creates detailed, bite-sized implementation plans from specs or requirements, with file structure, task decomposition, and TDD steps.

Provides civil infrastructure and construction domain knowledge, covering materials, project phases, building systems, contracts, site development, and regulatory requirements.

Create implementation-ready engineering plans for WelineFramework. Use in Plan mode, or when the user requests detailed requirements, code modification points, task cards, test cases, acceptance criteria, risk and rollback design, or a handoff package for execution-oriented AI agents.

Use only when the request concerns standards, responsibility, complexity, smells, naming, refactoring catalogs, or task-plan rules; not routine work.

Runs a structured five-round brainstorm to capture actors, features, scope, constraints, and business rules before writing a spec.

Use when you have a spec or requirements for a multi-step task. Creates comprehensive implementation plans with bite-sized tasks, exact file paths, and complete code examples.

Retrieves Jira tickets, analyzes requirements, updates ticket status, adds comments, and transitions issues via MCP or direct REST API.

Runs a structured, multi-round brainstorm to capture actors, features, scope, constraints, and business rules for a project before writing a spec.

Co-constructs defined end states from vague goals through AI-proposed, user-shaped dialogue, building a GoalContract when neither party has a clear end state.

Turns a spec or requirements into a detailed, bite-sized implementation plan with exact file paths, code, and test steps for engineers with no codebase context.

Creates detailed, step-by-step implementation plans from specs or requirements, with task decomposition, file structure, and test-driven development instructions.

Drafts structured goal-loop prompts for long-running agent work with verifiable stop conditions, validation commands, and documentation requirements.

Use this skill when a driver is returning to safety-sensitive duty after a positive test or refusal. Covers the SAP clearance, RTD test requirements (observed collection), and Clearinghouse update sequence.

Coordinates a squad of specialized agents for software development, routing tasks and managing context across requirements, planning, architecture, implementation, review, testing, and deployment phases.

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

ScepticAgent packaging and Chrome Web Store publishing workflow. Use whenever the user wants to build the zip, package the extension, publish or submit to the Chrome Web Store, update the store listing, or deal with manifest/icon/permission requirements for publishing.

Work ZenTao bugs/tasks end to end, manage task lifecycle and hours, or read a linked story as development context: fetch details, handle the user's request, verify changes, and ask before committing or writing back to ZenTao. Supports single items and sequential batches. Use when the user references ZenTao (禅道) bugs, tasks, stories, requirements, task status, or task hours.