Skip to content

Add implement-from-spec skill for architecture-aware feature work#1043

Open
prashantbytesyntax wants to merge 2 commits into
add_skill_filesfrom
pr-1042-agent-implementation-skill
Open

Add implement-from-spec skill for architecture-aware feature work#1043
prashantbytesyntax wants to merge 2 commits into
add_skill_filesfrom
pr-1042-agent-implementation-skill

Conversation

@prashantbytesyntax

Copy link
Copy Markdown
Contributor

Summary

This stacks on top of #1042 by adding a new .claude skill focused on the end-to-end workflow we want AI agents to follow when implementing gProfiler changes from a design spec.

The new implement-from-spec skill teaches the agent to:

  • map a design spec onto the current gProfiler architecture before editing code
  • prefer extending the smallest existing flow instead of creating a parallel path
  • use the current dynamic profiling / command-control path (heartbeat.py, command_control.py, continuous.py, ad_hoc.py) as the default seam for command-driven changes
  • bootstrap local validation with the repo's existing harness (./tests/test.sh, ./scripts/copy_resources_from_image.sh) instead of inventing custom setup
  • choose targeted tests first, then broaden to executable / full regression runs only when the scope requires it
  • review changes against today's architecture and shared hotspots such as main.py, tests/conftest.py, and queue-priority semantics

Why a new skill

The draft skills in #1042 already cover architecture, testing, review, and heartbeat individually, but they do not yet give an agent one clear workflow for:

  1. implementing from a spec
  2. selecting the correct existing code path
  3. validating locally with the repo-native setup
  4. avoiding regressions in shared orchestration / test infrastructure

This skill fills that gap without making the existing draft skills much longer.

Test plan

  • Keep the new skill concise (SKILL.md is 155 lines)
  • Cross-check file references and line counts against the current repo
  • Confirm local setup and test commands match CONTRIBUTING.md and tests/test.sh
  • Confirm command-control guidance matches the current dynamic profiling files and heartbeat tests

Made with Cursor

prashantbytesyntax and others added 2 commits June 4, 2026 23:32
Teach the agent how to turn a design spec into a minimal gProfiler
change by mapping it onto the current architecture, choosing the
smallest existing flow to extend, and validating the result locally.
The skill adds concrete guidance for command-control changes,
repo-native test bootstrap, targeted-vs-broad test selection, and
regression-aware review before handoff.

Co-authored-by: Cursor <cursoragent@cursor.com>
Bring the draft skills closer to the current gProfiler codebase by
teaching the dynamic profiling architecture, fixing stale heartbeat
references and required flags, adding architecture-aware code review
checks, and documenting a staged local test strategy that reuses the
repo's existing harness before broader regression runs.

Co-authored-by: Cursor <cursoragent@cursor.com>
@mlim19

mlim19 commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

@prashantbytesyntax, looks good to me. If you want, go ahead combine it with my PR. Or, I can do it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants