Results for “implementation”

Takes a new customer from signature to working — setting a definition of live that both sides agreed before the contract was signed, planning and staffing the implementation, running data migration and integration realistically, training the people who will actually use it, and handing over to the ongoing relationship. Use this to design an onboarding motion, rescue a stalled implementation, work out why customers who bought never went live, or scope the services a deal actually needs.

The English summary is being prepared. Showing the original description.

AI DevKit · Analyze and simplify existing implementations to reduce complexity, improve maintainability, and enhance scalability. Use when users ask to simplify code, reduce complexity, refactor for readability, clean up implementations, improve maintainability, reduce technical debt, or make code easier to understand.

The English summary is being prepared. Showing the original description.

Converts an arxiv paper into a minimal, citation-anchored Python implementation. Trigger when user runs /paper2code with an arxiv URL or paper ID, says "implement this paper", or pastes an arxiv link asking for implementation. Flags all ambiguities honestly. Never invents implementation details not stated in the paper.

The English summary is being prepared. Showing the original description.

Create if-then implementation intentions and WOOP plans for specific student behaviour change goals. Use when students know what to do but struggle to follow through on habits or routines.

The English summary is being prepared. Showing the original description.

Assess and operationalize implementation readiness for high-risk AI systems under the EU AI Act Annex III, including provider and deployer obligations, conformity assessment, post-market monitoring, and EU database registration. Use when users say things like “we classified this as high-risk, what now?”, “build an EU AI Act readiness plan”, “assess our Annex III compliance gaps”, “what do providers/deployers of high-risk AI need to implement?”, “prepare for conformity assessment”, or “create a high-risk AI implementation roadmap.”

The English summary is being prepared. Showing the original description.

Generate protocol/interface test suites that any implementation must pass. Define the contract once, test every implementation. Use when designing protocols or swapping implementations.

The English summary is being prepared. Showing the original description.

Generates detailed implementation guide with pseudo-code and step-by-step development instructions. Creates IMPLEMENTATION_GUIDE.md from PRD, Architecture, and UX specs. Use when creating development roadmap.

The English summary is being prepared. Showing the original description.

Master orchestrator that generates all implementation specs (PRD, Architecture, UX, Implementation, Test, Release) from product plan. Use when generating complete specification package.

The English summary is being prepared. Showing the original description.

An implementation, which takes input data and makes it available for proper batch effect removal by ComBat or Limma. The implementation appropriately handles missing values by dissecting the input matrix into smaller matrices with sufficient data to feed the ComBat or limma algorithm. The adjusted data is returned to the user as a rebuild matrix. The implementation is meant to make as much data available as possible with minimal data loss.

The English summary is being prepared. Showing the original description.

Run the post-implementation quality assurance workflow including tests, code polishing, review, and commit. Use when the user asks to "finalize implementation", "finalize changes", "wrap up implementation", "finish up", "ready to commit", or "run QA workflow".

The English summary is being prepared. Showing the original description.

Produce an implementation plan at .turbo/plans/<slug>.md. Use when the user asks to "draft a plan", "draft the plan", "write an implementation plan", "plan this change", "create an implementation plan", or needs a first-draft plan file before refinement.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. All plans MUST be validated using the included validation script. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.

The English summary is being prepared. Showing the original description.

Generates phased, dependency-ordered implementation tasks from specifications. Use after spec is complete and before starting implementation.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

Guides privacy law change monitoring and impact assessment for multi-jurisdiction organisations. Covers regulatory tracking sources, change classification, impact scoring methodology, and implementation prioritisation. Keywords: law monitoring, regulatory tracking, change management, impact assessment, implementation priority.

The English summary is being prepared. Showing the original description.

Guides conversion of gap analysis findings into phased implementation plans with milestones and risk-based prioritisation. Activate when building compliance programmes or allocating privacy budgets. Keywords: remediation roadmap, implementation plan, phased approach, prioritisation.

The English summary is being prepared. Showing the original description.

Perform the repository's risk-tiered independent final review before implementation completion. Use only when explicitly invoked or when repository instructions require it after behavior-impacting implementation work; audit the complete task diff, supported contracts, lifecycle and security boundaries, complexity, and tests before final verification.

The English summary is being prepared. Showing the original description.

Start and carry an explicitly invoked openai-guardrails-python implementation through a fresh isolated worktree and a local PR-ready handoff. Fetch the latest origin/main, keep task changes uncommitted, replay them onto the latest main before final review, run applicable verification and $implementation-final-review, use $pr-draft-summary to generate the complete PR draft and branch name, then create one clean local commit with takeover provenance when applicable. Use only when the user explicitly invokes this skill; never push, open a PR, or mutate GitHub.

The English summary is being prepared. Showing the original description.

Builds traceability matrices connecting requirements to design documents to source code implementation, tracking the complete development lifecycle. Use when you need to verify implementation completeness, ensure all requirements are implemented in code, generate compliance documentation, audit requirement coverage, identify orphaned code, or create traceability reports for stakeholders. Supports parsing requirements from Markdown, Word, and PDFs; extracting design from architecture docs and API specs; and scanning source code for implementations. Outputs to Markdown tables, Excel/CSV, and HTML visualizations.

The English summary is being prepared. Showing the original description.

Plan, implement, or review slo implementation work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests slo implementation work.

The English summary is being prepared. Showing the original description.

Plan, implement, or review hybrid search implementation work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests hybrid search implementation work.

The English summary is being prepared. Showing the original description.

Execute implementation within EPICs following test-first development, continuous SoT updates, and code traceability during PRD v0.7 Build Execution. Triggers on requests to start building, implement an epic, begin coding, or when user asks "start building", "implement epic", "coding", "development", "build execution", "implementation", "write code". Consumes EPIC- (context), TEST- (acceptance criteria). Updates existing IDs and creates code. Outputs working code with @implements traceability tags.

The English summary is being prepared. Showing the original description.

Battle-hardened NFT developer specializing in ERC-721/1155 implementations, gas-optimized minting, reveal mechanics, and marketplace integration. Has launched 50+ collections from stealth 1/1s to 10k PFP drops.Use when "build nft contract, mint function, erc721 implementation, erc1155 implementation, nft reveal, allowlist mint, dutch auction, lazy mint, on-chain metadata, royalty enforcement, operator filter, batch mint gas, token uri, soulbound token, nft, erc721, erc1155, erc721a, solidity, smart-contracts, opensea, blur, metadata, ipfs, arweave, royalties, minting, reveal, allowlist" mentioned.

The English summary is being prepared. Showing the original description.