dev-second-brain

Automate interrogation-driven coding assistance to generate implementation plans and code diffs.

1|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/josephrobertlopez/PromptEngineeringBootcamp --skill dev-second-brain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-second-brain
Source: https://github.com/josephrobertlopez/PromptEngineeringBootcamp/tree/main/skills/dev-second-brain
Command: npx skills add https://github.com/josephrobertlopez/PromptEngineeringBootcamp --skill dev-second-brain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Developer Second Brain automates the initial context gathering and planning for complex code tasks, enabling consistent, structured outputs that guide developers through code changes.

Core Features & Use Cases

  • Interrogation-Driven Workflow: Collects rich context through a structured interview to inform changes.
  • ReAct Pattern Implementation: Produces THINK/ACT/OBSERVE annotations for traceable decisions.
  • Structured Output Formats: Generates implementation plans, code diffs, test strategies, and checklists.
  • Bootcamp Integration: Useful in role-fork exercises and advanced patterns discussions.

Quick Start

Answer the 12–15 interrogation questions to generate a structured implementation plan with annotated thinking and actionable code diffs.

Frequently Asked Questions about dev-second-brain

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

FAQPage Schema
How do I plan complex code migrations and feature implementations?

Planning complex code migrations requires gathering rich context through a structured interrogation workflow to generate structured implementation plans, code diffs, and test strategies aligned to team conventions.

What is the ReAct pattern for structured code development output?

The ReAct pattern for structured code development produces THINK/ACT/OBSERVE annotations to trace decisions, ensuring implementation plans and systematic debugging steps are transparent and logically sequential.

How do I start an interrogation-driven coding workflow for refactoring?

To start interrogation-driven refactoring, answer the 12 to 15 interrogation questions to collect project context, which then generates a structured implementation plan with annotated thinking and actionable code diffs.

Can I use this interrogation workflow for systematic debugging across contemporary codebases?

Yes, the interrogation workflow supports systematic debugging across contemporary codebases by collecting detailed context to produce structured outputs and actionable code diffs for resolving complex issues.

Does this structured output approach work for React pattern implementation?

Yes, this approach works for React pattern implementation by applying the interrogation framework to gather context, producing structured implementation plans and code diffs aligned to your specific conventions.

What are the limitations of interrogation-driven coding assistance?

Interrogation-driven coding assistance requires completing a 12 to 15 question interview before generating outputs, making it less suitable for rapid, trivial code changes that do not need structured implementation plans.