Claude Skills by pedropacheco95

Ingest a transcript, RFP, brief or contract into project memory. "add this to project memory".

Build, extract or refresh the codebase insight layer. "extract insight", "map this codebase".

Run a named Cortex maintenance loop.

Register or activate this project''s cortex scheduled tasks in the Claude Desktop app.

Turn a half-formed idea into an agreed spec. "I want to add X", "how should we approach".

Diagnose a bug to its root cause and file it. "X is broken", "why does X happen", test triage.

Multi-pass codebase onboarding.

Execute a plan into code, verified by tests. "implement this spec", "build this slice".

Classify every incoming user request against the project's spec tree (developer specs in `.specflow/specs/`, business specs in `.specflow/specs-business/`, and `_overview.md` folder docs) and route it to the correct action before any work begins. This skill is the mandatory entry point for ALL user interactions in a Specflow-managed project (any project with a `.specflow/specs/` directory, with or without a parallel `.specflow/specs-business/`). PROACTIVELY use this skill whenever the user sa...

Reconcile an external document against the specs. "the client sent this", "ingest this".

Pin a verbatim ask with an anchor test. "pin this ask", "did the spec keep it".

Check and fix spec-tree structure. "lint specs", "validate the spec tree".

Spec out a new project from scratch — two linked spec trees, overviews, build order. "new project", "start a new", "I want to build", or any product idea described before any code exists.

Reverse-engineer specs from existing code. "onboard this codebase".

Turn an agreed spec into an executable plan. "plan this", "break this down", "what are the steps".

Verify review feedback before applying it. "here is the feedback".

Review a completed task diff for craft, anchored to its plan task and spec criterion. "review this", "review the diff", "code review". Correctness belongs to the tests, not to this review.

Write spec files — create, edit, link. "update the spec", "add this criterion".

Generate and run the four-layer test suite. "write tests", "generate tests from specs".

Generate the browsable spec site.

Evidence gate before claiming work done, fixed, or passing.

Ingest a transcript, RFP, brief or contract into project memory. "add this to project memory".

Build, extract or refresh the codebase insight layer. "extract insight", "map this codebase".

Run a named Cortex maintenance loop.

Register or activate this project''s cortex scheduled tasks in the Claude Desktop app.

Turn a half-formed idea into an agreed spec. "I want to add X", "how should we approach".

Diagnose a bug to its root cause and file it. "X is broken", "why does X happen", test triage.

Multi-pass codebase onboarding.

Execute a plan into code, verified by tests. "implement this spec", "build this slice".

Classify every incoming user request against the project's spec tree (developer specs in `.specflow/specs/`, business specs in `.specflow/specs-business/`, and `_overview.md` folder docs) and route it to the correct action before any work begins. This skill is the mandatory entry point for ALL user interactions in a Specflow-managed project (any project with a `.specflow/specs/` directory, with or without a parallel `.specflow/specs-business/`). PROACTIVELY use this skill whenever the user sa...

Reconcile an external document against the specs. "the client sent this", "ingest this".

Pin a verbatim ask with an anchor test. "pin this ask", "did the spec keep it".

Check and fix spec-tree structure. "lint specs", "validate the spec tree".

Spec out a new project from scratch — two linked spec trees, overviews, build order. "new project", "start a new", "I want to build", or any product idea described before any code exists.

Reverse-engineer specs from existing code. "onboard this codebase".

Turn an agreed spec into an executable plan. "plan this", "break this down", "what are the steps".

Verify review feedback before applying it. "here is the feedback".

Review a completed task diff for craft, anchored to its plan task and spec criterion. "review this", "review the diff", "code review". Correctness belongs to the tests, not to this review.

Write spec files — create, edit, link. "update the spec", "add this criterion".

Generate and run the four-layer test suite. "write tests", "generate tests from specs".

Generate the browsable spec site.

Evidence gate before claiming work done, fixed, or passing.