context-engineering

Name: context-engineering
Availability: InStock
Author: goodworkrinkz

Organize software development tasks into Research, Design, Plan, and Implement phases.

Updated Mar 23, 2026

Search Tags:#workflow #documentation #process #phases #software-engineering #context-management

Ready to run

npx skills add https://github.com/GOODWORKRINKZ/mylamp --skill context-engineering-goodworkrinkz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: context-engineering
Source: https://github.com/GOODWORKRINKZ/mylamp/tree/main/.agents/skills/context-engineering
Command: npx skills add https://github.com/GOODWORKRINKZ/mylamp --skill context-engineering-goodworkrinkz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Large codebases and complex tasks often lose context as teams pass work through several phases. This Skill provides a disciplined, multi-phase workflow (Research → Design → Plan → Implement) to capture, structure, and hand off context across phases.

Core Features & Use Cases

Phase-driven context management: Research gathers facts, Design defines architecture, Plan outlines work, Implement executes.
Clear documentation artifacts: research notes, design decisions, and implementation plans are generated for traceability.
Applicable for new features, bug fixes, and large-scale refactors in teams seeking predictable delivery and quality checks.

Quick Start

Provide a task from tasks.json and trigger the Research phase to collect facts.

Frequently Asked Questions about context-engineering

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

FAQPage Schema

How do I manage context loss in large software engineering projects?▼

Managing context loss in software engineering requires a phased workflow that captures facts and decisions into structured documentation before coding. This approach breaks work into Research, Design, Plan, and Implement cycles to preserve traceability across teams.

What is the best way to structure a software development workflow for complex refactoring?▼

The best way to structure complex refactoring is a four-phase cycle: Research gathers facts, Design defines architecture, Plan outlines work, and Implement executes. This enforces independent phase deliverables and peer reviews for predictable delivery.

How do I start the Research phase for a new software feature?▼

To start the Research phase for a new feature, provide a task from your tasks.json file and trigger the workflow. The phase will guide your team to collect facts and generate structured research notes before moving to design.

Can I use this phased workflow for bug fixes and new features?▼

Yes, you can use this phased workflow for bug fixes, new features, and large-scale refactors. It applies a disciplined context management process to ensure quality checks and structured documentation across various software engineering tasks.

What documentation artifacts are generated during the software development phases?▼

The documentation artifacts generated during the phases include research notes, design decisions, and implementation plans. These structured deliverables ensure traceability and enforce quality gates before progressing to the next phase.

Do I need mandatory frontmatter in SKILL.md for context management workflows?▼

Yes, you need mandatory frontmatter in SKILL.md to enforce guardrails for the workflow. This requirement ensures independent phase deliverables, peer reviews, and quality gates are properly documented and maintained throughout the process.