Results for “implementation”

Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.

Analyzes an app from video, screenshots, or description, then generates implementation stories in dependency order.

Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.

Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.

Create a detailed, phased implementation plan with documentation discovery. Use when asked to plan a feature, task, or multi-step implementation — especially before executing with do.

Applies Agile principles to software development, system design, and technical problem-solving, covering implementation, optimization, and best practices.

Guides implementation of new model architectures in NeMo AutoModel through five phases: discovery, implementation, registration, validation, and testing.

Guides the agent through structured protocols for writing technical specifications, implementation plans, and summaries, with file naming and task directory conventions.

Turns a mature product plan into a rough implementation plan with high-level steps, maturity and verification marks, and a risks section.

Turns a brief product idea into working, verified code by orchestrating requirements analysis, planning, parallel implementation, QA, and multi-perspective validation.

Breaks a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/.

Create a detailed, step-by-step implementation plan for a feature or project. Load when the user asks to plan a feature, create a technical roadmap, break down a PRD into tasks, design an implementation strategy, or sequence engineering work. Also triggers on "how should we build this", "implementation plan for", "technical breakdown", "task list for", or any request to turn a high-level requirement into a concrete execution plan. Supports phased rollouts, architecture-first, and MVP-focused planning.

Verifies each step of a rough implementation plan against source code and current documentation, attaching proof and marking steps as verified or unverified.

Implements work from a PRD or set of issues using TDD, typechecking, and regular testing, then reviews and commits the changes.

Transforms a rough idea into a detailed design document with an implementation plan through iterative requirements clarification, research, design, and planning.

Conducts structured requirements workshops to produce feature specifications, user stories, EARS-format functional requirements, acceptance criteria, and implementation checklists.

Surveys a codebase as a senior advisor and produces prioritized, self-contained implementation plans for other models or agents to execute, without modifying source code.

Use for rapid read-only discovery of files, APIs, and relevant implementation areas.

Decompose a single roadmap phase into implementation steps, tests, and file-level detail

Produces a plain-language stakeholder summary from an existing feature specification, for sharing with non-technical stakeholders before implementation kicks off. Use when the user wants to draft a stakeholder summary, executive summary, or business summary of a feature spec or PRD. Does not write the spec itself — use plan-a-feature. Does not sequence the build into phases — use plan-a-phased-build. Does not produce an implementation plan — use plan-implementation.

Turn an approved PRD or implementation goal into SRS/FRS technical requirements (How), architecture, contracts, and verification decisions.

Guides collaborative dialogue to turn ideas into approved designs and specs before any implementation begins.

Guides collaborative dialogue to turn ideas into approved designs and specs before any implementation begins.

Plan a feature from BRD-lite brief or clear intent into PRD (What), decisions, implementation plan, and task slices.

Guides collaborative dialogue to turn ideas into approved designs and specs before any implementation begins.

Guides collaborative dialogue to turn ideas into fully formed designs and specs before any implementation begins.

Guides collaborative dialogue to turn ideas into designs and specs, exploring intent and requirements before any implementation.

Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation.

Shape a rough product or project idea into a scoped brief before customer discovery, market research, specifications, UX, UI, or implementation planning

Guides collaborative dialogue to turn ideas into fully formed designs and specs, exploring intent, requirements, and design before implementation.