pre-implementation-code-orientation

Name: pre-implementation-code-orientation
Availability: InStock
Author: exception-coder

Extract code coordinates from documentation and map them to file paths.

6|1|Updated Mar 30, 2026

Search Tags:#documentation #pre-implementation #design-docs #source-reading #code-coordinates #bug-docs

Ready to run

npx skills add https://github.com/exception-coder/team-standards --skill pre-implementation-code-orientation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pre-implementation-code-orientation
Source: https://github.com/exception-coder/team-standards/tree/main/skills/pre-implementation-code-orientation
Command: npx skills add https://github.com/exception-coder/team-standards --skill pre-implementation-code-orientation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures a strict handoff from documentation to code by loading pre-embedded coordinates before any implementation begins, preventing re-scans and misaligned changes.

Core Features & Use Cases

Extract and validate code coordinates from design and bug documentation.
Map coordinates to concrete file paths and line numbers in the repository.
Produce a precise, implementation-ready plan that guides coding tasks.

Quick Start

Review the design or bug documentation to extract embedded code coordinates and generate a ready-to-use implementation plan before editing any source files.

Frequently Asked Questions about pre-implementation-code-orientation

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

FAQPage Schema

How do I map design docs to specific file paths and line numbers before coding?▼

Mapping design docs to specific file paths and line numbers involves extracting pre-embedded code coordinates from the documentation and applying them to selectively read key source files, producing a precise implementation plan without scanning entire codebases.

What are code coordinates in bug documentation and how do they work?▼

Code coordinates in bug documentation are embedded location references that pinpoint exact source file targets. They work by enabling selective reading of key code sections, which anchors implementation changes directly to the documentation.

How do I prevent re-scanning entire source files when starting implementation from design docs?▼

To prevent re-scanning entire source files during implementation, load and validate the pre-embedded code coordinates within your design documentation to selectively read only the mapped file paths and line numbers required for the coding task.

Can I generate an implementation-ready plan directly from bug docs?▼

Yes, you can generate an implementation-ready plan directly from bug docs by identifying and loading the embedded code coordinates, mapping them to concrete file paths and line numbers to produce a precise coding plan.

Does this approach require coordinates to already exist in the design documentation?▼

Yes, this approach requires code coordinates to already be embedded in the design or bug documentation, as the process extracts and validates these pre-existing references to ensure a strict handoff from documentation to code.

What is the best way to ensure a strict handoff from documentation to code implementation?▼

The best way to ensure a strict handoff from documentation to code is to load pre-embedded code coordinates before any implementation begins, anchoring work to the documentation and outputting a precise plan that prevents misaligned changes.